diff options
| author | Rui Ueyama <ruiu@google.com> | 2016-02-08 05:18:44 +0000 |
|---|---|---|
| committer | Rui Ueyama <ruiu@google.com> | 2016-02-08 05:18:44 +0000 |
| commit | be748c2033b39afbd559166d2209c1c712b896b3 (patch) | |
| tree | 3e708668389fb5c17e03a71cd230e804a50d9535 /lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp | |
| parent | b4fd8bb27ed60106f359264ae13137a9bc8f412b (diff) | |
| download | bcm5719-llvm-be748c2033b39afbd559166d2209c1c712b896b3.tar.gz bcm5719-llvm-be748c2033b39afbd559166d2209c1c712b896b3.zip | |
ELF: Simplify getFdeEncoding.
I found that the handling of 'L' character in an augmentation string is
wrong because 'L' means that the next byte is the length field. I could
have fixed that by just skipping the next byte, but I decided to take a
different approach.
Teaching the linker about all the types of CIE internal records just to
skip them is silly. And the code doing that is not actually executed now
(that's why the bug did not cause any issue.) It is because the 'R' field,
which we want to read, is always at beginning of the CIE. So I reduced
the code dramatically by assuming that that's always the case. I want to
see how it works in the wild. If it doesn't work, we can roll this back
(with a fix for 'L').
http://reviews.llvm.org/D16939
llvm-svn: 260073
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp')
0 files changed, 0 insertions, 0 deletions
