diff options
| author | Jan Kratochvil <jan.kratochvil@redhat.com> | 2020-02-10 10:29:26 +0100 |
|---|---|---|
| committer | Jan Kratochvil <jan.kratochvil@redhat.com> | 2020-02-10 10:29:32 +0100 |
| commit | 1a39f1b966a8d8f15ed0d5a832d5097cccefe93b (patch) | |
| tree | 02e94bd0674a8d45efe3521cdde964dbee9ff2c3 /llvm/lib/Object/ELFObjectFile.cpp | |
| parent | 6115bd9ba2851469d372d0d7b36d87a3e1d8094b (diff) | |
| download | llvm-1a39f1b966a8d8f15ed0d5a832d5097cccefe93b.zip llvm-1a39f1b966a8d8f15ed0d5a832d5097cccefe93b.tar.gz llvm-1a39f1b966a8d8f15ed0d5a832d5097cccefe93b.tar.bz2 | |
[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
Diffstat (limited to 'llvm/lib/Object/ELFObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions