Do I need the Android NDK installed?

While the skill can identify frames without it, having the Android NDK or an LLVM toolchain installed is required to run the actual symbolication via llvm-symbolizer.

Can this handle Java-only Android crashes?

No, this skill is specifically designed for symbolicating native frames within the .NET runtime components like Mono and CoreCLR.

Can it symbolicate managed C# exceptions?

No, managed exceptions are usually already readable in logcat. This tool is specifically for native-level signals where the stack trace only shows memory addresses.

Does it work with .NET MAUI?

Yes, it is ideal for triaging native crashes in .NET MAUI, Xamarin.Android, and other .NET-based Android apps.

Where does the skill get the debug symbols?

It extracts ELF BuildIds from your crash log and automatically downloads the matching symbols from the official Microsoft symbol server.

Android Tombstone Symbolicator

Name: Android Tombstone Symbolicator
Author: dotnet

bydotnet

•

1,215

•

Mobile Development

Resolves native Android crash tombstones into readable .NET runtime function names and source code locations.

This skill automates the complex process of symbolicating native backtraces from .NET Android app crashes, including MAUI and Mono-based applications. It parses tombstone files or logcat output to extract ELF BuildIds, automatically fetches the correct debug symbols from Microsoft’s official symbol servers, and utilizes LLVM tools to map memory addresses to specific function names, source files, and line numbers. It is an essential tool for developers triaging low-level runtime crashes like SIGSEGV or SIGABRT that occur within the .NET runtime components on Android devices.

주요 기능

01Direct integration with Microsoft's symbol server for seamless debug symbol retrieval

02Detailed mapping of backtrace frames to .NET runtime (Mono/CoreCLR) source code

03Automated BuildId and PC offset extraction from Android tombstone files and logcat logs

04Support for various LLVM toolchains including the Android NDK's llvm-symbolizer

05Identification of specific .NET runtime versions and Git source commits from BuildIds

061,215 GitHub stars

사용 사례

01Triaging native crashes such as SIGSEGV or SIGABRT in .NET MAUI or Xamarin.Android applications

02Resolving unreadable native backtrace frames into actionable source file and line number information

03Debugging low-level issues within the Mono or CoreCLR runtime on Android

주요 기능

01Direct integration with Microsoft's symbol server for seamless debug symbol retrieval

02Detailed mapping of backtrace frames to .NET runtime (Mono/CoreCLR) source code

03Automated BuildId and PC offset extraction from Android tombstone files and logcat logs

04Support for various LLVM toolchains including the Android NDK's llvm-symbolizer

05Identification of specific .NET runtime versions and Git source commits from BuildIds

061,215 GitHub stars

사용 사례

01Triaging native crashes such as SIGSEGV or SIGABRT in .NET MAUI or Xamarin.Android applications

02Resolving unreadable native backtrace frames into actionable source file and line number information

03Debugging low-level issues within the Mono or CoreCLR runtime on Android