James Henderson 40bfd37ca7 [DWARF] Don't attempt to parse line tables at invalid offsets ... Whilst working on improvements to the error handling of the debug line parsing code, I noticed that if an invalid offset were to be specified in a call to getOrParseLineTable(), an entry in the LineTableMap would still be created, even if the offset was not within the section range. The immediate parsing attempt afterwards would fail (it would end up getting a version of 0), and thereafter, any subsequent calls to getOrParseLineTable or getLineTable would return the default- constructed, invalid line table. In reality, we shouldn't even attempt to parse this table, and we should always return a nullptr from these two functions for this situation. I have tested this via a unit test, which required some new framework for unit testing debug line. My plan is to add quite a few more unit tests for the new error reporting mechanism that will follow shortly, hence the reason why the supporting code for the tests are written the way they are - I intend to extend the DwarfGenerator class to support generating debug line. At that point, I'll make sure that there are a few positive test cases for this and the parsing code too. Differential Revision: https://reviews.llvm.org/D44200 Reviewers: JDevlieghere, aprantl llvm-svn: 326995		2018-03-08 10:53:34 +00:00
..
CodeView	Remove redundant includes from unittests.	2017-12-13 21:31:05 +00:00
DWARF	[DWARF] Don't attempt to parse line tables at invalid offsets	2018-03-08 10:53:34 +00:00
MSF	[MSF] Fix FPM interval calcluation	2018-01-05 18:12:14 +00:00
PDB	[DebugInfoPDB] Add DIA implementation for getSrcLineOnTypeDefn	2018-03-07 00:33:09 +00:00
CMakeLists.txt	[MSF] Move MSF unit tests to their own unittest target.	2017-08-02 22:26:09 +00:00