diff options
| author | Hafiz Abid Qadeer <hafiz_abid@mentor.com> | 2017-05-25 10:21:29 +0000 |
|---|---|---|
| committer | Hafiz Abid Qadeer <hafiz_abid@mentor.com> | 2017-05-25 10:21:29 +0000 |
| commit | 0b5d6e5d0e093377e3b212093b999c3fec9c2b69 (patch) | |
| tree | 4f1168ddd20d66d85c659f4e711e4283b8a7a9ce /lldb/packages/Python/lldbsuite/test/expression_command | |
| parent | 1db4c88a9a5ecd6917d2be64438f4b03306f3073 (diff) | |
| download | bcm5719-llvm-0b5d6e5d0e093377e3b212093b999c3fec9c2b69.tar.gz bcm5719-llvm-0b5d6e5d0e093377e3b212093b999c3fec9c2b69.zip | |
Fix FDE indexing while scan debug_info section.
There are some differences between eh_frame and debug_frame formats that
are not considered by DWARFCallFrameInfo::GetFDEIndex. An FDE entry
contains CIE_pointer in debug_frame in same place as cie_id in eh_frame.
As described in dwarf standard (section 6.4.1), CIE_pointer is an
"offset into the .debug_frame section". So, variable cie_offset should
be equal cie_id for debug_frame.
FDE entries with zeroth CIE pointer (which is actually placed in cie_id
variable) shouldn't be ignored also.
I have also added a little change which allow to use debug_info section
when eh_frame is absent. This case really can take place on some platforms.
Patch from tatyana-krasnukha.
https://reviews.llvm.org/D33504
llvm-svn: 303847
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command')
0 files changed, 0 insertions, 0 deletions
