diff options
| author | Peter Collingbourne <peter@pcc.me.uk> | 2019-11-01 18:48:59 -0700 |
|---|---|---|
| committer | Peter Collingbourne <peter@pcc.me.uk> | 2019-11-04 09:11:14 -0800 |
| commit | 2c6fae179e6984c7330ff8a284d7a10ce142eef9 (patch) | |
| tree | eafd4a1874afe07564a7e4de0e8fa8f63a3cbce4 /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp | |
| parent | 664f84e246478db82be2871f36fd1a523d9f2731 (diff) | |
| download | bcm5719-llvm-2c6fae179e6984c7330ff8a284d7a10ce142eef9.tar.gz bcm5719-llvm-2c6fae179e6984c7330ff8a284d7a10ce142eef9.zip | |
ELF: Discard .ARM.exidx sections for empty functions instead of misordering them.
The logic added in r372781 caused ARMExidxSyntheticSection::addSection()
to return false for exidx sections without a link order dep that passed
isValidExidxSectionDep(). This included exidx sections for empty functions. As
a result, such exidx sections would end up treated like ordinary sections and
would end up being laid out before the ARMExidxSyntheticSection, most likely in
the wrong order relative to the exidx entries in the ARMExidxSyntheticSection,
breaking the orderedness invariant relied upon by unwinders. Fix this by
simply discarding such sections.
Differential Revision: https://reviews.llvm.org/D69744
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp')
0 files changed, 0 insertions, 0 deletions
