diff options
| author | Stefan Gränitz <stefan.graenitz@gmail.com> | 2020-11-10 11:36:59 +0100 |
|---|---|---|
| committer | Stefan Gränitz <stefan.graenitz@gmail.com> | 2020-11-10 11:37:53 +0100 |
| commit | 203b4774b88322de22c99881a3e1e4c78a9d5a0e (patch) | |
| tree | e67bad2b37d6048f5b1582c7877235da22617c64 /lldb/packages/Python/lldbsuite/test/dotest.py | |
| parent | a75d6178b809cf11d54af91e8e1254064d58f6eb (diff) | |
| download | llvm-203b4774b88322de22c99881a3e1e4c78a9d5a0e.zip llvm-203b4774b88322de22c99881a3e1e4c78a9d5a0e.tar.gz llvm-203b4774b88322de22c99881a3e1e4c78a9d5a0e.tar.bz2 | |
[lldb][ObjectFile] Relocate sections for in-memory objects (e.g. received via JITLoaderGDB)
Part 2 of a fix for JITed code debugging. This has been a regression from 5.0 to 6.0 and it's still reproducible on current master: https://bugs.llvm.org/show_bug.cgi?id=36209 Part 1 was D61611 a while ago.
The in-memory object files we obtain from JITLoaderGDB are not yet relocated. It looks like this used to happen on the LLDB side and my guess is that it broke with D38142. (However, it's hard to tell because the whole thing was broken already due to the bug in part 1.) The patch moved relocation resolution to a later point in time and didn't apply it to in-memory objects. I am not aware of any reason why we wouldn't resolve relocations per-se, so I made it unconditional here. On Debian, it fixes the bug for me and all tests in `check-lldb` are still fine.
Reviewed By: labath
Differential Revision: https://reviews.llvm.org/D90769
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/dotest.py')
0 files changed, 0 insertions, 0 deletions