Martin Storsjö 7d019d1a3b [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		2019-12-02 22:42:00 +02:00
..
API	[LLDB] Always remove debugserver from LLVM_DISTRIBUTION_COMPONENTS	2019-11-12 12:58:26 -08:00
Shell	[LLDB] Set the right address size on output DataExtractors from ObjectFile	2019-12-02 22:42:00 +02:00
Unit	[CMake] Split logic across test suite subdirectories (NFC)	2019-10-24 10:58:22 -07:00
CMakeLists.txt	[lldb] Mark ASan & TSan as test dependencies	2019-11-06 15:24:49 -08:00
lit.cfg.py	[test] Cleanup top-level lit.cfg.py	2019-10-10 19:51:47 +00:00
lit.site.cfg.py.in	Re-land "[test] Split LLDB tests into API, Shell & Unit"	2019-10-09 19:22:02 +00:00