summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
diff options
context:
space:
mode:
authorJames Henderson <jh7370@my.bristol.ac.uk>2019-03-12 17:00:25 +0000
committerJames Henderson <jh7370@my.bristol.ac.uk>2019-03-12 17:00:25 +0000
commit9bc817a0ae7d629417e369c0612b6312b7437dfa (patch)
treeda86078606248c98ca2a51053feabff3a426cbd6 /lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
parent149bc099f61a81a37751622c1b6d405fddb46204 (diff)
downloadbcm5719-llvm-9bc817a0ae7d629417e369c0612b6312b7437dfa.tar.gz
bcm5719-llvm-9bc817a0ae7d629417e369c0612b6312b7437dfa.zip
[yaml2obj]Allow explicit symbol indexes in relocations and emit error for bad names
Prior to this change, the "Symbol" field of a relocation would always be assumed to be a symbol name, and if no such symbol existed, the relocation would reference index 0. This confused me when I tried to use a literal symbol index in the field: since "0x1" was not a known symbol name, the symbol index was set as 0. This change falls back to treating unknown symbol names as integers, and emits an error if the name is not found and the string is not an integer. Note that the Symbol field is optional, so if a relocation doesn't reference a symbol, it shouldn't be specified. The new error required a number of test updates. Reviewed by: grimar, ruiu Differential Revision: https://reviews.llvm.org/D58510 llvm-svn: 355938
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud