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
..
2023-03-18 16:01:09 -07:00
2023-04-05 23:22:29 -07:00
2023-01-26 16:36:13 -07:00
2023-01-26 16:36:14 -07:00
2023-02-04 15:19:53 -05:00
2022-11-04 00:09:27 +03:30