4 ms·
I wonder what effect stripping has on crash dump reports though. I don’t know enough about how the App Store manages those, like (if a user opts in to “share in
by abotsis 5y ago
I wonder what effect stripping has on crash dump reports though. I don’t know enough about how the App Store manages those, like (if a user opts in to “share information with the developer”), does the developer get less nice dumps as a result of stripping? Surely this can be worked around so long as someone has a symbol table (which they likely do), but the infrastructure might not be in place to do that automatically.
- mlindner 5y agoA good crash dump doesn't need symbols at all. The symbols come from the stored symbols from when the author originally compiled it. As long as the builds are reproducible you can even produce the symbols at a later date for an old version if you still have the source code.
- snovv_crash 5y agoEven if the builds aren't reproducible, rebuilding on the same machine with the same settings usually gives you something a crash dump will work with. But, make your builds reproducible and/or save your debug symbols as part of your release process, it will be something you wish you did otherwise when you're not quite sure if the stack trace you have is correct.
- ajconway 5y agoDebug symbols are stored separately on the developer’s computer (and may be uploaded to Apple, but that’s optional). Including symbols in the App Store binary is practically useless.
- hoten 5y agoIs there any reason Apple couldn't just strip the code binaries themselves?
- ajconway 5y agoNo, Apple already modifies uploaded binaries before storing them for distribution. In some cases Apple even compiles the binaries themselves (if the developer chose to include the LLVM "bitcode" when submitting the app).