Community
Participate
Working Groups
Build Identifier: DwarfInfoReader uses the line entries table in setupAddresses to work out what ranges of memory are covered by the compile unit. Unfortunately some compilers do not correctly garbage collect line entry tables for functions which have been garbage collected resulting in erroneous line entry regions starting at or near 0. Calling fixupRanges after using the line entry tables to initially compute the start and end address fixes this up and removes the invalid region(s). I have a patch which adds this. Reproducible: Always
Created attachment 200744 [details] Fixup the ranges after using line entries as a first attempt
Created attachment 200781 [details] Additionally move compileUnitHeader registration earlier as this is required.
the patch has been merged and nominally tested in our local source base. waiting for final review and merge to eclipse edc git repository by committer Ken Ryall.
Fixed in: http://git.eclipse.org/c/cdt/org.eclipse.cdt.edc.git/commit/?id=f7c4790c134d0cdc30cdbe8d2a016bf27cd25528