aboutsummaryrefslogtreecommitdiff
path: root/lldb/scripts/Python/modify-python-lldb.py
diff options
context:
space:
mode:
authorAlexey Lapshin <a.v.lapshin@mail.ru>2019-02-27 13:17:36 +0000
committerAlexey Lapshin <a.v.lapshin@mail.ru>2019-02-27 13:17:36 +0000
commit77fc1f6049a7414ec193c9ff8226eeb5662a5878 (patch)
treeb2bffed96e676b25942dbe39194e0f08a153f638 /lldb/scripts/Python/modify-python-lldb.py
parentef920358277603c69f4f548d2e5c40842972dd71 (diff)
downloadllvm-77fc1f6049a7414ec193c9ff8226eeb5662a5878.zip
llvm-77fc1f6049a7414ec193c9ff8226eeb5662a5878.tar.gz
llvm-77fc1f6049a7414ec193c9ff8226eeb5662a5878.tar.bz2
[DebugInfo] add SectionedAddress to DebugInfo interfaces.
That patch is the fix for https://bugs.llvm.org/show_bug.cgi?id=40703 "wrong line number info for obj file compiled with -ffunction-sections" bug. The problem happened with only .o files. If object file contains several .text sections then line number information showed incorrectly. The reason for this is that DwarfLineTable could not detect section which corresponds to specified address(because address is the local to the section). And as the result it could not select proper sequence in the line table. The fix is to pass SectionIndex with the address. So that it would be possible to differentiate addresses from various sections. With this fix llvm-objdump shows correct line numbers for disassembled code. Differential review: https://reviews.llvm.org/D58194 llvm-svn: 354972
Diffstat (limited to 'lldb/scripts/Python/modify-python-lldb.py')
0 files changed, 0 insertions, 0 deletions