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-04-30 18:16:04 -07:00
2023-05-26 21:42:19 -07:00
2023-04-30 18:16:04 -07:00
2023-05-23 17:55:59 -07:00
2023-05-29 13:04:55 +03:00
2023-05-23 17:55:59 -07:00
2022-12-13 13:14:20 +02:00
2023-04-30 18:16:04 -07:00
2023-05-26 21:42:19 -07:00
2023-04-22 13:09:15 +03:00
2023-05-23 17:55:59 -07:00
2023-04-30 18:16:04 -07:00
2023-04-30 18:16:04 -07:00
2023-04-30 18:16:04 -07:00
2023-05-23 17:55:59 -07:00
2023-05-23 17:55:59 -07:00
2023-05-23 17:55:59 -07:00
2023-04-30 18:16:04 -07:00
2023-04-30 18:16:04 -07:00
2023-04-23 21:06:21 +03:00
2023-04-23 21:06:21 +03:00
2023-05-23 17:55:59 -07:00
2023-03-17 17:50:25 +01:00
2023-04-28 13:24:43 -07:00
2023-05-26 21:42:19 -07:00
2023-04-30 18:16:04 -07:00