android-tombstone-symbolication

Symbolicate Android tombstone backtraces to map native frames to .NET symbols.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill android-tombstone-symbolication-sayedihashimi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-tombstone-symbolication
Source: https://github.com/sayedihashimi/copilot-skill-eval/tree/main/examples/aspnet-razor-pages/plugins/dotnet-skills/dotnet-diag/skills/android-tombstone-symbolication
Command: npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill android-tombstone-symbolication-sayedihashimi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Symbolicate native frames from Android tombstones to reveal .NET runtime symbols, enabling faster crash triage.

Core Features & Use Cases

  • Symbolicates tombstone backtraces using ELF BuildIds and Microsoft's symbol server.
  • Downloads and applies debug symbols for libmonosgen-2.0.so, libcoreclr.so, and related .NET runtime libraries.
  • Useful for triaging MAUI, Xamarin, or Mono Android crashes and correlating native frames to source.

Quick Start

Run the Symbolicate-Tombstone.ps1 script with a tombstone file 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, run the Symbolicate-Tombstone.ps1 script with your tombstone file to map native frames to .NET symbols using ELF BuildIds and Microsoft's symbol server. This produces a symbolicated backtrace for faster crash triage.

What is Android tombstone symbolication and when do I need it for Xamarin crashes?

Android tombstone symbolication maps native crash frames to .NET runtime symbols. You need it when triaging MAUI, Xamarin, or Mono Android crashes to correlate native frames from libraries like libmonosgen-2.0.so back to your source code.

Do I need llvm-symbolizer and a symbol server to symbolicate Android tombstones?

Yes, you need llvm-symbolizer and access to the Microsoft symbol server to symbolicate Android tombstones. The script downloads debug symbols per BuildId for .NET runtime libraries and caches them locally for the symbolication process.

Can I use this tombstone symbolication process for Mono Android crash scenarios?

Yes, you can symbolicate tombstones for Mono Android crash scenarios. The process applies to MAUI, Xamarin, and Mono Android crashes, downloading and applying debug symbols for libmonosgen-2.0.so and libcoreclr.so to reveal .NET runtime symbols.

How does the tombstone symbolication script handle debug symbols and BuildIds?

The script uses ELF BuildIds from the tombstone to query Microsoft's symbol server, downloading matching debug symbols for .NET runtime libraries. These symbol files are cached locally so llvm-symbolizer can map native frames to .NET symbols.

What's the best way to map native frames from an Android tombstone to source code?

The best way to map native frames to source is running Symbolicate-Tombstone.ps1 with your tombstone file. It leverages llvm-symbolizer and Microsoft's symbol server to download debug symbols via BuildIds, producing a symbolicated backtrace for triage.