android-tombstone-symbolication

Symbolicate Android tombstone backtraces to .NET frames for crash triage.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/kierunb/ReliableAppDemo --skill android-tombstone-symbolication-kierunb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-tombstone-symbolication
Source: https://github.com/kierunb/ReliableAppDemo/tree/main/.github/skills/dotnet-diag/skills/android-tombstone-symbolication
Command: npx skills add https://github.com/kierunb/ReliableAppDemo --skill android-tombstone-symbolication-kierunb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires System.IO.Compression, and includes scripts (resource) components.

What problem does it solve?

Symbolicates Android tombstone native backtraces to .NET frames to aid crash triage for MAUI, Xamarin, and Mono Android apps.

Core Features & Use Cases

  • Symbolicate native backtrace frames to function names and source locations using ELF BuildIds and Microsoft symbol server.
  • Map .NET runtime libraries (libmonosgen-2.0.so, libcoreclr.so, libSystem.*.so) to .NET source code for faster debugging.
  • Use in crash triage scenarios involving SIGABRT, SIGSEGV, and other native signals in Android apps.

Quick Start

Run the Symbolicate-Tombstone.ps1 script with a tombstone file and a path to llvm-symbolizer to produce a symbolicated backtrace.

Frequently Asked Questions about android-tombstone-symbolication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I symbolicate an Android tombstone backtrace for a .NET MAUI app?

To symbolicate an Android tombstone backtrace for a .NET MAUI app, run the Symbolicate-Tombstone.ps1 script with a tombstone file and a path to llvm-symbolizer to map native frames to source lines.

What is needed to map Xamarin Android native crash frames to source code?

Mapping Xamarin Android native crash frames requires a tombstone input file, internet access for symbol downloads from the Microsoft symbol server, and llvm-symbolizer to resolve ELF BuildIds to source locations.

Does this symbolication process work with Mono Android SIGSEGV crashes?

Yes, the symbolication process works with Mono Android SIGSEGV crashes by mapping .NET runtime libraries like libmonosgen-2.0.so and libcoreclr.so to source code for faster debugging and crash triage.

Can I use a local symbol cache to symbolicate tombstones without internet access?

You can use local symbol caches to symbolicate tombstones, but internet access is required for initial symbol downloads from the Microsoft symbol server to map BuildIds to source lines.

What's the best way to identify the .NET runtime version from an Android tombstone?

The best way to identify the .NET runtime version from an Android tombstone is using the symbolication script's runtime version lookups, which report the exact version when mapping native library frames.