summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorUlrich Weigand <ulrich.weigand@de.ibm.com>2016-04-14 14:36:29 +0000
committerUlrich Weigand <ulrich.weigand@de.ibm.com>2016-04-14 14:36:29 +0000
commitbd5262629dcb00ab17cfa5331e3815a3eeff8124 (patch)
tree482ee64727bce555ec7b17c7223b3bbb75604ae7 /lldb/packages/Python/lldbsuite/test
parent7e8de59b9059a2eec1367f32c0a06561f5e025ac (diff)
downloadbcm5719-llvm-bd5262629dcb00ab17cfa5331e3815a3eeff8124.tar.gz
bcm5719-llvm-bd5262629dcb00ab17cfa5331e3815a3eeff8124.zip
Find .plt section in object files generated by recent ld
Code in ObjectFileELF::ParseTrampolineSymbols assumes that the sh_info field of the .rel(a).plt section identifies the .plt section. However, with recent GNU ld this is no longer true. As a result of this: https://sourceware.org/bugzilla/show_bug.cgi?id=18169 in object files generated with current linkers the sh_info field of .rel(a).plt now points to the .got.plt section (or .got on some targets). This causes LLDB to fail to identify any PLT stubs, causing a number of test case failures. This patch changes LLDB to simply always look for the .plt section by name. This should be safe across all linkers and targets. Differential Revision: http://reviews.llvm.org/D18973 llvm-svn: 266316
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud