-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Store debug symbols #12485
Comments
afaik and not an expert on this topic, when we build a release build, |
Maybe when @kkaefer gets back he can take a look at this? I don't know how or even where Android build configuration happens, but I can't think of a reason we wouldn't be able to build release with symbols. |
What kind of builds do you want to symbolicate? |
I've been tracing through the NDK build process as part of binary size optimization. Here's what I've found:
What we probably want to do is archive one of the unstripped intermediates. Bloaty has a command to read symbol sizes from a stripped binary and names from another, and this works with these files, e.g.:
|
Picking this up before the final 6.4.0 release tomorrow so we are able to use these .so files to look into bugreports. In #12628, I'm storing the .so files as circle-ci artefact. At some point I would love to move them to AWS S3 for ease of access. |
Need to relook into which .so files we are using for running ndk-stack on as the ones currently stored do not result in useable traces: eg. below a trace that lists
|
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
At the moment, we are unable to symbolicate stack traces that weren't reproduced on a local machine. We need to look into ways of storing symbols when building and releasing a new version and whether it's possible to symbolicate provided, external stack traces.
The text was updated successfully, but these errors were encountered: