skills.rest
paleoterra
paleoterraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

crash-log-analyzer

Parse macOS crash logs to identify crash causes and debugging information.

2|Updated Jun 25, 2023
Search Tags:#debugging#troubleshooting#stack trace#analysis#macos#symbolication#crash logs
One-click install
npx skills add https://github.com/paleoterra/PaleoRose --skill crash-log-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crash-log-analyzer
Source: https://github.com/paleoterra/PaleoRose/tree/main/.claude/skills/crash-log-analyzer
Command: npx skills add https://github.com/paleoterra/PaleoRose --skill crash-log-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual, time-consuming process of sifting through complex macOS crash logs, quickly identifying root causes and providing actionable debugging information.

Core Features & Use Cases

  • Automated Analysis: Parse .crash and .ips files, symbolicate stack traces, and identify crash types (e.g., EXC_BAD_ACCESS).
  • Contextual Debugging: Extract thread information, show crash location, and identify common crash patterns.
  • Use Case: Automatically analyze a user-submitted .crash file, symbolicate the stack trace, and provide a summary of the probable cause and a recommendation for a fix, saving hours of manual debugging.

Quick Start

Analyze the attached crash log file 'app_crash_2025-11-08.crash' and provide a summary.

Frequently Asked Questions about crash-log-analyzer

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

FAQPage Schema
How do I analyze macOS crash logs to find the root cause?▼

Parse .crash and .ips files to extract crash type, exception details, thread context, and stack trace. Symbolication with dSYM translates memory addresses into readable function names, revealing exactly where and why the crash occurred, enabling targeted debugging.

Can I symbolicate stack traces without manually decoding addresses?▼

Yes. Automatic symbolication with dSYM files converts raw memory addresses into function names and source locations. The Skill handles this during parsing, producing human-readable stack traces that pinpoint the crash location instantly.

What's the best way to batch-analyze multiple crash logs at once?▼

Process entire directories of .crash and .ips files together. The Skill batch-analyzes collections, identifies duplicate crashes across files, and exports structured JSON summaries with crash type, exception, probable cause, and recommendations for each file.

How do I identify duplicate crashes across multiple crash log files?▼

The Skill detects duplicate crashes by comparing crash patterns, exception types, and stack traces across a batch of files. This reveals whether reported crashes are isolated incidents or recurring issues affecting stability.

Can I export crash analysis results in a structured format?▼

Yes. Export parsed crash data as JSON with comprehensive Crash Summary details: process, bundle, version, date, crash type, exception, crashed thread, stack trace, probable cause, and actionable recommendations.

Do I need dSYM files to debug macOS crashes effectively?▼

dSYM files are essential for symbolication—converting opaque memory addresses into readable function names and line numbers. Without them, stack traces remain unreadable. The Skill integrates dSYM symbolication to produce actionable debugging information.

Related Skills

Explore More Software Engineering Skills→
ojrojasojrojas

apple-crash-symbolication

Automates .NET runtime frame symbolication in Apple platform crash logs using dSYM files and atos.

Community
Advanced
Paxeer-NetworkPaxeer-Network
3

sentry-analysis

Analyze Sentry crash reports and implement evidence-based bug fixes.

Official
Advanced
conorluddyconorluddy
179

crash-debugging

Symbolicate iOS crash logs with dSYM files to identify root causes.

Community
Intermediate
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced