mlugg 46e724ab28 std.dwarf: handle DWARF 5 compile unit DW_AT_ranges correctly ...

This data changed quite significantly between DWARF 4 and 5. Some
systems are shipping DWARF 5 libraries (Void Linux on musl libc seems to
use it for crt1 etc), which meant when printing stack traces, a random
compile unit might be incorrectly identified as containing an address,
resulting in incorrect location information.

I was consistently experiencing this issue with compiler stack traces,
and this change fixed it.

2023-05-29 11:28:39 -07:00

58 KiB

Raw Blame History

View Raw