diff options
| author | George Rimar <grimar@accesssoftek.com> | 2018-11-14 13:01:15 +0000 |
|---|---|---|
| committer | George Rimar <grimar@accesssoftek.com> | 2018-11-14 13:01:15 +0000 |
| commit | 004bcb78ed532ff9897b757f35e02ec1b802ff00 (patch) | |
| tree | d5b477b6d16809654e01ea4c5601ddd34deecf18 /lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py | |
| parent | cdb170794be637bb278cda421e37c5f71bd3cf1a (diff) | |
| download | bcm5719-llvm-004bcb78ed532ff9897b757f35e02ec1b802ff00.tar.gz bcm5719-llvm-004bcb78ed532ff9897b757f35e02ec1b802ff00.zip | |
[LLDB] - Recommit r346848 "[LLDB] - Support the single file split DWARF.".
Test cases were updated to not use the local compilation dir which
is different between development pc and build bots.
Original commit message:
[LLDB] - Support the single file split DWARF.
DWARF5 spec describes a single file split dwarf case
(when .dwo sections are in the .o files).
Problem is that LLDB does not work correctly in that case.
The issue is that, for example, both .debug_info and .debug_info.dwo
has the same type: eSectionTypeDWARFDebugInfo. And when code searches
section by type it might find the regular debug section
and not the .dwo one.
The patch fixes that. With it, LLDB is able to work with
output compiled with -gsplit-dwarf=single flag correctly.
Differential revision: https://reviews.llvm.org/D52403
llvm-svn: 346855
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py')
0 files changed, 0 insertions, 0 deletions
