diff options
| author | George Rimar <grimar@accesssoftek.com> | 2019-09-17 13:58:46 +0000 |
|---|---|---|
| committer | George Rimar <grimar@accesssoftek.com> | 2019-09-17 13:58:46 +0000 |
| commit | a3569aced05dd0238e286283da46bb55cd1f4c83 (patch) | |
| tree | f894b5bfa84d477462d10f0fd57efa70f18e8b2f /lldb/packages/Python/lldbsuite/test/commands/expression/call-function/TestCallStdStringFunction.py | |
| parent | f1d069e54df350a807e9b90462485483139327ea (diff) | |
| download | bcm5719-llvm-a3569aced05dd0238e286283da46bb55cd1f4c83.tar.gz bcm5719-llvm-a3569aced05dd0238e286283da46bb55cd1f4c83.zip | |
[llvm-readobj/llvm-objdump] - Improve how tool locate the dynamic table and report warnings about that.
Before this patch we gave a priority to a dynamic table found
from the section header.
It was discussed (here: https://reviews.llvm.org/D67078?id=218356#inline-602082)
that probably preferring the table from PT_DYNAMIC is better,
because it is what runtime loader sees.
This patch makes the table from PT_DYNAMIC be chosen at first place if it is available.
But also it adds logic to fall back to SHT_DYNAMIC if the table from the dynamic segment is
broken or fall back to use no table if both are broken.
It adds a few more diagnostic warnings for the logic above.
Differential revision: https://reviews.llvm.org/D67547
llvm-svn: 372122
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/expression/call-function/TestCallStdStringFunction.py')
0 files changed, 0 insertions, 0 deletions
