diff options
| author | Tamas Berghammer <tberghammer@google.com> | 2015-09-16 12:36:37 +0000 |
|---|---|---|
| committer | Tamas Berghammer <tberghammer@google.com> | 2015-09-16 12:36:37 +0000 |
| commit | 6127f033581a1fbb853bc36cdb57e62b8dd9bbe3 (patch) | |
| tree | a9c5a9a248dbfb606c355c5d01d38ceee2ae20f0 /lldb/source/Plugins/OperatingSystem/Python/OperatingSystemPython.cpp | |
| parent | 6dabac88db39aa100cb0bc56aef19a2233f8b6a3 (diff) | |
Fix prologue end handling when code compiled by gcc
GCC don't use the is_prologue_end flag to mark the first instruction
after the prologue. Instead of it it is issuing a line table entry for
the first instruction of the prologue and one for the first instruction
after the prologue. If the size of the prologue is 0 instruction then
the 2 line entry will have the same file address.
We remove these duplicates entries as they are violating the dwarf spec
and can cause confusion in the debugger. To prevent the lost of
information about the end of prologue we should set the prologue end
flag for the line entries what are representing more then 1 entry.
Differential revision: http://reviews.llvm.org/D12757
llvm-svn: 247788
Diffstat (limited to 'lldb/source/Plugins/OperatingSystem/Python/OperatingSystemPython.cpp')
0 files changed, 0 insertions, 0 deletions