aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authorGeorge Rimar <grimar@accesssoftek.com>2018-08-21 08:13:06 +0000
committerGeorge Rimar <grimar@accesssoftek.com>2018-08-21 08:13:06 +0000
commite2684662ee16a6b6b26353c2c8a13dcec894b2cd (patch)
treee827d105b69a3a51dcf9b210fae3c09b5c8ba1c8 /lldb/packages/Python/lldbsuite/test/configuration.py
parent097ef69182d65c6687822a2a846bf82de5cf2686 (diff)
downloadllvm-e2684662ee16a6b6b26353c2c8a13dcec894b2cd.zip
llvm-e2684662ee16a6b6b26353c2c8a13dcec894b2cd.tar.gz
llvm-e2684662ee16a6b6b26353c2c8a13dcec894b2cd.tar.bz2
[LLD][ELF] - Check the architecture of lazy objects earlier.
Our code in LazyObjFile::parse() has an ELFT switch and adds a lazy object by its ELFT kind. Though it might be possible to add a file using a different architecture and make LLD to silently accept it (if the file is empty or contains only week symbols). That itself, not a huge issue perhaps (because the error would be reported later if the file is fetched), but still does not look clean and correct. It is possible to report an error earlier and clean up the code. That is what the patch does. Ideally, we might want to reuse isCompatible from SymbolTable.cpp, but it is static and accepts a file as an argument, what is not convenient. Since such a situation should be rare, I think it should be OK to go with the way chosen in this patch. Differential revision: https://reviews.llvm.org/D50899 llvm-svn: 340257
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions