diff options
author | Martin Storsjö <martin@martin.st> | 2019-11-29 13:28:25 +0200 |
---|---|---|
committer | Martin Storsjö <martin@martin.st> | 2019-12-02 22:42:00 +0200 |
commit | 7d019d1a3be252a885e8db1ee7af11c90b450d38 (patch) | |
tree | 42724473f8feba2e6af38b6d60a57bfa0563663c /lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h | |
parent | afd5d912812e6f2ea99c8890676d47a01bbcfbb1 (diff) | |
download | bcm5719-llvm-7d019d1a3be252a885e8db1ee7af11c90b450d38.tar.gz bcm5719-llvm-7d019d1a3be252a885e8db1ee7af11c90b450d38.zip |
[LLDB] Set the right address size on output DataExtractors from ObjectFile
If filling in a DataExtractor from an ObjectFile, e.g. via the
ReadSectionData method, the output DataExtractor gets the address
size from the m_data member.
ObjectFile's m_data member is initialized without knowledge about
the address size (so the address size is set based on the host's
sizeof(void*), and at that point within ObjectFile's constructor,
virtual methods implemented in subclasses (like GetAddressByteSize())
can't be called, therefore fix it up when filling in external
DataExtractors.
This makes sure that line tables from executables with a different
address size are parsed properly; previously this tripped up
DWARFDebugLine::LineTable::parse for 32 bit executables on a 64 bit
host, as the address size in the line table (4) didn't match the
one set in the DWARFDataExtractor.
Differential Revision: https://reviews.llvm.org/D70848
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h')
0 files changed, 0 insertions, 0 deletions