[Bug symtab/28200] DW_AT_ranges handling in partial_die_info::read does not handle discontinuous ranges

["simark at simark dot ca" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28200

--- Comment #6 from Simon Marchi <simark at simark dot ca> ---
Here's my interpretation of your post, just to make sure I understand
correctly.

I. Looks correct
II. Looks correct
III. Now it sounds like bad debug info, because the CU's ranges is not a
superset of its children.  Unless GDB knows better (producer X produces wrong
CU ranges), I think it is correct to trust the CU's ranges, so the result shown
looks correct.  (I wouldn't mind having a maintenance mode where we compute the
ranges from the CU's children even if the CU has ranges, and compare the two
address maps to see if there's a difference.  That could mean a bug in GDB or
in the debug info.)
IV. When the CU doesn't provide ranges, we fall back on building an address map
that is the intersection of everything found under the CU.  At this point it
looks correct, because you still haven't put a "hole" in the function's ranges.
V. Now that you've put a hole in the function's ranges, we should see the hole,
therefore it's incorrect.

-- 
You are receiving this mail because:
You are on the CC list for the bug.