diff options
| author | mlugg <mlugg@mlugg.co.uk> | 2023-05-26 07:14:54 +0100 |
|---|---|---|
| committer | Andrew Kelley <andrew@ziglang.org> | 2023-05-29 11:28:39 -0700 |
| commit | 46e724ab28ba5934471d8b2dec60acdd7885d64b (patch) | |
| tree | aa4469c776d972e512c8bc046fc8c68dd4864abe /src/codegen/spirv/TypeConstantCache.zig | |
| parent | 1697d44809151e4759f6b5f9447a908c30ac1e84 (diff) | |
| download | zig-46e724ab28ba5934471d8b2dec60acdd7885d64b.tar.gz zig-46e724ab28ba5934471d8b2dec60acdd7885d64b.zip | |
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.
Diffstat (limited to 'src/codegen/spirv/TypeConstantCache.zig')
0 files changed, 0 insertions, 0 deletions