diff options
| author | Marcin Koscielnicki <koriakin@0x04.net> | 2016-04-14 21:19:27 +0000 |
|---|---|---|
| committer | Marcin Koscielnicki <koriakin@0x04.net> | 2016-04-14 21:19:27 +0000 |
| commit | 9e09355477e163fa739090587101bcfaf91f98da (patch) | |
| tree | 21be5236653cf9d77cf1bd8d039799960458f712 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp | |
| parent | 20bf94209e49c716af6935505ea46d95ee67159d (diff) | |
| download | bcm5719-llvm-9e09355477e163fa739090587101bcfaf91f98da.tar.gz bcm5719-llvm-9e09355477e163fa739090587101bcfaf91f98da.zip | |
[sanitizer] [SystemZ] Fix stack traces.
On s390, the return address is in %r14, which is saved 14 words from
the frame pointer.
Unfortunately, there's no way to do a proper fast backtrace on SystemZ
with current LLVM - the saved %r15 in fixed-layout register save
area points to the containing frame itself, and not to the next one.
Likewise for %r11 - it's identical to %r15, unless alloca is used
(and even if it is, it's still useless). There's just no way to
determine frame size / next frame pointer. -mbackchain would fix that
(and make the current code just work), but that's not yet supported
in LLVM. We will thus need to XFAIL some asan tests
(Linux/stack-trace-dlclose.cc, deep_stack_uaf.cc).
Differential Revision: http://reviews.llvm.org/D18895
llvm-svn: 266371
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
