android-tombstone-symbolication

Run the Symbolicate-Tombstone.ps1 script with the tombstone file path and llvm-symbolizer. It parses backtrace frames, downloads debug symbols from the Microsoft symbol server by BuildId, and resolves each .NET frame to a function name and source line.

Extract the BuildId and PC offset from the tombstone frame, download the matching .debug file from the Microsoft symbol server using the elf-buildid-sym URL format, then run llvm-symbolizer with the debug file and offset to get the function and source location.

llvm-symbolizer ships with the Android NDK under toolchains/llvm/prebuilt/*/bin/. It is also available via brew install llvm, apt install llvm, or xcrun on macOS. Use LLVM 14 or newer for best DWARF compatibility.

Logcat-captured tombstones often omit BuildIds. Recover them via adb shell readelf -n on the device library, CI build artifacts, or the runtime NuGet package. Pulling raw tombstones from /data/tombstones/ always includes BuildIds.

NativeAOT statically links the runtime into the app binary, so only libSystem.*.so BCL frames resolve via the symbol server; the app binary needs its own debug symbols. Pure Java/Kotlin crashes and managed exceptions visible in logcat are out of scope.

Pre-release or internal .NET builds may not publish symbols to the Microsoft symbol server. Check for local unstripped .so or .so.dbg files in build artifacts or the NuGet runtime pack instead.