authorgravatar for kubkon@jakubkonka.comJakub Konka <kubkon@jakubkonka.com> 2021-11-30 16:48:49+01:00
committergravatar for kubkon@jakubkonka.comJakub Konka <kubkon@jakubkonka.com> 2021-11-30 16:48:49+01:00
log28623544ce78c5c559af8a47c62e688db9ce5e4a
tree603cb1f5d80a01b11fea21365a9a8b61c5210364
parenta56749b654bbe432752a57e130c7cf9dda370a15

macos: remove >= 0x10000000 assertion when printing stack traces

I don't think we can guarantee that especially for system dyld dylibs which can be loaded at any address (perhaps even some OS preferential low memory address). Incidentally, this fixes stack trace tests on x86_64 macOS 12.

1 files changed, 0 insertions(+), 1 deletions(-)

lib/std/debug.zig-1
...@@ -1412,7 +1412,6 @@ pub const ModuleDebugInfo = switch (native_os) {...@@ -1412,7 +1412,6 @@ pub const ModuleDebugInfo = switch (native_os) {
1412 nosuspend {1412 nosuspend {
1413 // Translate the VA into an address into this object1413 // Translate the VA into an address into this object
1414 const relocated_address = address - self.base_address;1414 const relocated_address = address - self.base_address;
1415 assert(relocated_address >= 0x100000000);
14161415
1417 // Find the .o file where this symbol is defined1416 // Find the .o file where this symbol is defined
1418 const symbol = machoSearchSymbols(self.symbols, relocated_address) orelse1417 const symbol = machoSearchSymbols(self.symbols, relocated_address) orelse