I'm sure I'm doing something wrong with the defer - since I'm catching errors already
zachcarter, what happened is you returned an error from main, so zig is trying to print an error return trace, to show where the error came from (although in this case it is trivially obvious) and the debug info code itself has panicked and triggered a stack trace, which then succeeds and shows where in zig's debug info code it failed
so it's a bug in zig standard library with regards to macos stack traces
gotcha - just wanted to make sure that it was already known about, and if not to raise it :) thanks for the explanation
enjoying zig so far :) coming from C++ and Nim
emekoi: I know how it works in C..... the question is how we can apply attributes to memory and/or allocators in zig. It's more than executuable too: not all memory is the same. e.g. on some architectures, some memory is faster to access than others. you might decide to have 'persistant' memory. huge pages exist...