[lldb] Skip Recognizer/assert.test on linux-> PR56144
[lldb] [test] Update test status for NetBSD
[lldb] Enable FreeBSDRemote plugin by default and update test statusThe new FreeBSDRemote plugin has reached feature parity on i386and amd64 targets. Use it by default on these architectures, whi
[lldb] Enable FreeBSDRemote plugin by default and update test statusThe new FreeBSDRemote plugin has reached feature parity on i386and amd64 targets. Use it by default on these architectures, whileallowing the use of the legacy plugin via FREEBSD_LEGACY_PLUGIN envvar.Revisit the method of switching plugins. Apparently, the return valueof PlatformFreeBSD::CanDebugProcess() is what really decides whetherthe legacy or the new plugin is used.Update the test status. Reenable the tests that were previouslydisabled on FreeBSD and do not cause hangs or are irrelevant to FreeBSD.Mark all tests that fail reliably as expectedFailure. For now, teststhat are flaky (i.e. produce unstable results) are left enabledand cause unpredictable test failures.Differential Revision: https://reviews.llvm.org/D90757
show more ...
[lldb/Test] Skip recognizer tests when Python is disabledThe `frame recognizer` command only exists when Python scripting isenabled. Therefore the test should be made conditional on Python.Withou
[lldb/Test] Skip recognizer tests when Python is disabledThe `frame recognizer` command only exists when Python scripting isenabled. Therefore the test should be made conditional on Python.Without it, the test fails with "'frame recognizer' is not a knowncommand."
[LLDB] Fix typo in xfail decorator assert.testFix a typo in earlier xfailed assert.test replace // with #.
[LLDB] Mark some xfails for arm-linuxThis patch marks following tests as xfail for arm-linux target.lldb/test/API/functionalities/load_using_paths/TestLoadUsingPaths.pylldb/test/API/python_api/t
[LLDB] Mark some xfails for arm-linuxThis patch marks following tests as xfail for arm-linux target.lldb/test/API/functionalities/load_using_paths/TestLoadUsingPaths.pylldb/test/API/python_api/thread/TestThreadAPI.pylldb/test/Shell/Recognizer/assert.testBugs have been filed for all of them for the corresponding failingcomponent.
[lldb/test] Add alternate symbol to StackFrame RecognizerThis reimplements commit 6b2979c12300b90a1e69791d43ee9cff14f4265e and updatesthe tests to reflect the addition of the alternate symbol attr
[lldb/test] Add alternate symbol to StackFrame RecognizerThis reimplements commit 6b2979c12300b90a1e69791d43ee9cff14f4265e and updatesthe tests to reflect the addition of the alternate symbol attribute.Signed-off-by: Med Ismail Bennani <[email protected]>
Revert "[lldb] Fix+re-enable Assert StackFrame Recognizer on Linux"This reverts commit 1a39f1b966a8d8f15ed0d5a832d5097cccefe93b asit breaks macOS.
[lldb] Fix+re-enable Assert StackFrame Recognizer on LinuxD73303 was failing on Fedora Linux and so it was disabled by Skip theAssertFrameRecognizer test for Linux.I find no easy way how to find
[lldb] Fix+re-enable Assert StackFrame Recognizer on LinuxD73303 was failing on Fedora Linux and so it was disabled by Skip theAssertFrameRecognizer test for Linux.I find no easy way how to find out if it gets recognized as`__assert_fail` or `__GI___assert_fail` as during `Process` ctorlibc.so.6 is not yet loaded by the debuggee.DWARF symbol `__GI___assert_fail` overrides the ELF symbol `__assert_fail`.While external debug info (=DWARF) gets disabled for testsuite (D55859)that sure does not apply for real world usage.Differential Revision: https://reviews.llvm.org/D74252
Revert "[lldb] Fix+re-enable Assert StackFrame Recognizer on Linux"This reverts commit cf1046c716b33ed449aa8fc26376864917c63c25.Reverted: https://reviews.llvm.org/D74252It fixed testsuite but br
Revert "[lldb] Fix+re-enable Assert StackFrame Recognizer on Linux"This reverts commit cf1046c716b33ed449aa8fc26376864917c63c25.Reverted: https://reviews.llvm.org/D74252It fixed testsuite but broke real world functionality where is not used: settings set symbols.enable-external-lookup false
[lldb] Fix+re-enable Assert StackFrame Recognizer on LinuxD73303 was failing on Fedora Linux and so it was disabled by Skip theAssertFrameRecognizer test for Linux.On Fedora 30 x86_64 I have:
[lldb] Fix+re-enable Assert StackFrame Recognizer on LinuxD73303 was failing on Fedora Linux and so it was disabled by Skip theAssertFrameRecognizer test for Linux.On Fedora 30 x86_64 I have: $ readelf -Ws /lib64/libc.so.6 |grep '^Symbol\|.*assert_fail' Symbol table '.dynsym' contains 2362 entries: 630: 0000000000030520 70 FUNC GLOBAL DEFAULT 14 __assert_fail@@GLIBC_2.2.5 Symbol table '.symtab' contains 22711 entries: 922: 000000000002275a 15 FUNC LOCAL DEFAULT 14 __assert_fail_base.cold 18044: 0000000000030520 70 FUNC LOCAL DEFAULT 14 __GI___assert_fail 20081: 00000000000303a0 370 FUNC LOCAL DEFAULT 14 __assert_fail_base 21766: 0000000000030520 70 FUNC GLOBAL DEFAULT 14 __assert_failThe patch should never expect __GI___assert_fail:.symtab can be present or not but that should not change that__assert_fail always wins - it is always present from .dynsym and it cannever be overriden by __GI___assert_fail as __GI___assert_fail has onlylocal binding. Global binding is preferred since D63540.External debug info symbols do not matter since D55859 (and DWARF shouldnever be embedded in system libc.so.6).Differential Revision: https://reviews.llvm.org/D74252
[lldb/test] Skip the AssertFrameRecognizer test for LinuxThis patch skips the AssertFrameRecognizer test for Linux since it appears tofail on certain distributions (AFAIK Fedora & ArchLinux).The
[lldb/test] Skip the AssertFrameRecognizer test for LinuxThis patch skips the AssertFrameRecognizer test for Linux since it appears tofail on certain distributions (AFAIK Fedora & ArchLinux).The failure happen because the thread don't set the current frame tothe most relevant one. So the stopped location doesn't match with whatthe test is expecting.The test will be enabled again after I'll be able to reproduce the failureon one of those platform and fix the issue.Signed-off-by: Med Ismail Bennani <[email protected]>
[lldb/Target] Add Assert StackFrame RecognizerWhen a thread stops, this checks depending on the platform if the top frame isan abort stack frame. If so, it looks for an assert stack frame in the u
[lldb/Target] Add Assert StackFrame RecognizerWhen a thread stops, this checks depending on the platform if the top frame isan abort stack frame. If so, it looks for an assert stack frame in the upperframes and set it as the most relavant frame when found.To do so, the StackFrameRecognizer class holds a "Most Relevant Frame" and a"cooked" stop reason description. When the thread is about to stop, it checksif the current frame is recognized, and if so, it fetches the recognized frame'sattributes and applies them.rdar://58528686Differential Revision: https://reviews.llvm.org/D73303Signed-off-by: Med Ismail Bennani <[email protected]>
Revert "[lldb/Target] Add Assert StackFrame Recognizer"This reverts commit 2b7f32892b76cdfbe075300a5bf4a52e1b674bc7 because of testfailures due to dangling pointers.
Revert "[lldb/Target] Add Assert StackFrame Recognizer"This reverts commit 03a6b858fde5c644ec16b1fddd8e10aa9ef3f0ad.The test doesn't pass on Debian.