summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/source-manager
diff options
context:
space:
mode:
authorGeorge Rimar <grimar@accesssoftek.com>2017-05-03 08:21:42 +0000
committerGeorge Rimar <grimar@accesssoftek.com>2017-05-03 08:21:42 +0000
commit99e1890e71b27fac5999a6cb7f78305b83f9cb1f (patch)
tree9c28593148acc05ca0c7d3903127c2cd9a13a21f /lldb/packages/Python/lldbsuite/test/source-manager
parent72684bbaf5be316acf264f8fba66874acdc3ef56 (diff)
downloadbcm5719-llvm-99e1890e71b27fac5999a6cb7f78305b83f9cb1f.tar.gz
bcm5719-llvm-99e1890e71b27fac5999a6cb7f78305b83f9cb1f.zip
[ELF] - Added testcase gdb-index-ranges.s (https://reviews.llvm.org/D32750)
Before rL301170 was landed, LLD did not produce correct entries in .gdb_index address area. Issue was fixed on LLVM DWARF parsers side and was relative to how .debug_ranges section was scanned. It was main problem of PR32319. It makes sense to have testcase on LLD size too. This checks that we generate proper values now, because we do not have any tests for .gdb_index which works with .debug_ranges atm. Differential revision: https://reviews.llvm.org/D32750 llvm-svn: 302006
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/source-manager')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud