android-native-crash-analysis

To analyze an Android native crash, you provide the tombstone file and project path to the skill, which then parses the crash artifact, applies strict symbolization rules, and generates a detailed source-based crash analysis report for diagnostics.

Android NDK crash symbolization often fails due to incorrect module, ABI, or NDK path resolution; this skill enforces project-aware resolution to accurately map addresses to source code across diverse packaging layouts.

The best way to parse logcat logs for native crash root causes is using an AI-assisted workflow that combines deterministic CLI resolution with symbolic analysis, ensuring accurate identification of the crash source.

Yes, you can use local CLI tools to symbolicate Android native crash reports; this skill coordinates deterministic project resolution with local tools to interpret tombstone and logcat formats efficiently.

Yes, you need to resolve ABI and NDK paths for accurate native crash analysis; the skill uses project-aware resolution to map the crash context correctly and enforce strict symbolization rules.

Without strict symbolization, analyzing native crashes yields inaccurate root cause identification and obscured source mapping; this skill enforces symbolization rules to prevent such diagnostic failures across varying project contexts.