stack trace implementation for MACH-O #434
Labels
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
standard library
This issue involves writing Zig code for the standard library.
Milestone
Currently if you cause a safety violation in an ELF binary, zig gives you a nice stack trace. Not so for MACH-O binaries.
It appears to still be DWARF information, so that code could be reused, but it's not stored directly in the binary - there's some kind of mapping from binary to .o files where the actual debug info is stored.
The text was updated successfully, but these errors were encountered: