3 ms·
In my experience you would strip the symbols out of the prod binary, and save them separately somewhere. Then your production binary will give you stack traces
by umanwizard 7y ago
In my experience you would strip the symbols out of the prod binary, and save them separately somewhere.
Then your production binary will give you stack traces like [0x12345, 0xabcde, ...], but you can use the separately-stored files to symbolicate them and get the source file/line info.
Not sure if this is possible on all platforms but it at least is for all combinations of {C, C++, Objective-C, Rust} and { Linux, macOS, iOS } .
And if that added operational complexity is not worth the size savings, you can freely choose not to do it, and things will work like they do in Go.