- I want to symbolicate a call stack from a crash on my Android (IL2CPP) production build in libil2cpp.so, but I have been unable to find the symbols for that library.
You haven't enabled symbol generation in the build settings window.
In the build settings window, you should see an option to generate a .zip with your symbols when you create a build:
After a build is completed, the symbols zip file should be in the same folder as the apk.
The Public Symbols package contains the information needed to resolve function addresses to human-readable strings. Because it doesn't contain debug information, it's much smaller than the Debugging Symbols package.
The Debugging Symbols package contains complete debugging information and a symbol table. Use it to:
- Resolve stack traces and debug apps for which you have source code available.
- Place breakpoints and debug the code with the native debugger.
If your Unity version doesn't have an option to generate symbols, you can find the symbols after each build at ProjectFolder\Temp\StagingArea\libs\[architecture]
For more information, consult the following documentation:
Is this still accurate? I'm trying to upload symbols to Crashlytics for Android IL2CPP build.
Do we definitely want "libil2cpp.so.debug" even for non development builds?
It seems like there is an error or "libil2cpp.so.debug" has been moved to "/StagingArea/symbols/"
how to get crash trace for a il2cpp build?
In old mono builds, I could use addr2line? in il2cpp builds? how to use libil2cpp.so.debug? why I always get meanningless line like "
??:0" in addr2line?
I also would like to know if anyone has figured out why some of the lines output by addr2line end up being empty and completely useless like this:
I've used both the libil2cpp.sym.so and the libunity.sym.so to get a parts of a call stack deobfuscated, but there are still gaps like the above - why? Are there more symbols Unity generates that we need to run through the addr2line tool?
Please sign in to leave a comment.