Jan Kratochvil 1a39f1b966 [lldb] Fix+re-enable Assert StackFrame Recognizer on Linux ... D73303 was failing on Fedora Linux and so it was disabled by Skip the AssertFrameRecognizer 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` ctor libc.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		2020-02-10 10:29:32 +01:00
..
API	[lldb/tests] Correctly configure the lldb dotest arguments	2020-02-06 10:27:10 -08:00
Shell	[lldb] Fix+re-enable Assert StackFrame Recognizer on Linux	2020-02-10 10:29:32 +01:00
Unit	[CMake] Split logic across test suite subdirectories (NFC)	2019-10-24 10:58:22 -07:00
CMakeLists.txt	[lldb/CMake] Set LLVM_HOST_TRIPLE from TARGET_TRIPLE in standalone builds.	2020-01-16 20:06:25 -08:00
lit.cfg.py	[test] Cleanup top-level lit.cfg.py	2019-10-10 19:51:47 +00:00
lit.site.cfg.py.in	Re-land "[test] Split LLDB tests into API, Shell & Unit"	2019-10-09 19:22:02 +00:00