원클릭으로 Manus에서 모든 스킬 실행

시작하기

crash-log-analyzer

스타2

포크0

업데이트2026년 6월 1일 00:03

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

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

paleoterra

paleoterra/PaleoRose

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Crash Log Analyzer

Parse macOS .crash and .ips files to extract useful debugging information.

Capabilities

Parse crash report files
Symbolicate stack traces
Identify crash type (EXC_BAD_ACCESS, assertion, etc.)
Extract thread information
Show crash location and context
Identify common crash patterns
Generate crash statistics
Find duplicate crashes
Export crash data

Tools Included

`crash_analyzer.py`

Python script to parse crash logs

Commands:

# Analyze crash log
./crash_analyzer.py crash.crash

# Symbolicate (requires dSYM)
./crash_analyzer.py crash.crash --dsym PaleoRose.app.dSYM

# Batch analyze directory
./crash_analyzer.py --batch ~/Library/Logs/DiagnosticReports/PaleoRose*

# Export summary
./crash_analyzer.py crash.crash --export-json summary.json

# Find duplicates
./crash_analyzer.py --find-duplicates ~/Library/Logs/DiagnosticReports/

Crash Types Handled

EXC_BAD_ACCESS (SIGSEGV, SIGBUS)
EXC_CRASH (SIGABRT)
Uncaught exceptions
Assertions
Watchdog timeouts
Stack overflow

Usage

Use when:

App crashes during testing
Need to analyze user crash reports
Debugging difficult-to-reproduce crashes
Tracking crash patterns
Preparing crash reports for issues

Output Format

Crash Summary
-------------
Process: PaleoRose
Bundle ID: com.example.paleorose
Version: 1.0.0
Date: 2025-11-08 20:30:15

Crash Type: EXC_BAD_ACCESS (SIGSEGV)
Exception: KERN_INVALID_ADDRESS at 0x0000000000000000

Crashed Thread: 0 (Main Thread)

Stack Trace:
  0  PaleoRose  0x10045a123 -[TableListController tableView:objectValueFor:row:] + 123
  1  AppKit     0x7fff2b3c4567 -[NSTableView _sendDataSourceValue] + 234
  2  AppKit     0x7fff2b3c4890 -[NSTableView reloadData] + 567

Probable Cause: Null pointer dereference in tableNames array access
Recommendation: Add nil check before accessing tableNames[row]

이 저장소의 다른 Skills

같은 저장소

documentation

paleoterra/PaleoRose

Generate comprehensive API documentation using DocC (Swift-DocC) for your PaleoRose project

2026-06-012

asset-catalog-optimizer

paleoterra/PaleoRose

Analyze and optimize Xcode asset catalogs - find unused assets, missing resolutions, compress images

2026-06-012

build-performance

paleoterra/PaleoRose

Analyze and optimize Xcode build times by identifying slow compilation units and suggesting improvements

2026-06-012

ci-cd-helper

paleoterra/PaleoRose

Generate CI/CD configurations and automation scripts for building, testing, and deploying

2026-06-012

code-metrics-analyzer

paleoterra/PaleoRose

Calculate code quality metrics - complexity, coverage, maintainability

2026-06-012

interface-builder-validator

paleoterra/PaleoRose

Parse and validate XIB/Storyboard files for broken outlets, warnings, accessibility

2026-06-012

name	crash-log-analyzer
description	Parse and analyze macOS crash logs to identify crash causes and debugging information
type	skill
language	python

Crash Log Analyzer

Parse macOS .crash and .ips files to extract useful debugging information.

Capabilities

Parse crash report files
Symbolicate stack traces
Identify crash type (EXC_BAD_ACCESS, assertion, etc.)
Extract thread information
Show crash location and context
Identify common crash patterns
Generate crash statistics
Find duplicate crashes
Export crash data

Tools Included

`crash_analyzer.py`

Python script to parse crash logs

Commands:

# Analyze crash log
./crash_analyzer.py crash.crash

# Symbolicate (requires dSYM)
./crash_analyzer.py crash.crash --dsym PaleoRose.app.dSYM

# Batch analyze directory
./crash_analyzer.py --batch ~/Library/Logs/DiagnosticReports/PaleoRose*

# Export summary
./crash_analyzer.py crash.crash --export-json summary.json

# Find duplicates
./crash_analyzer.py --find-duplicates ~/Library/Logs/DiagnosticReports/

Crash Types Handled

EXC_BAD_ACCESS (SIGSEGV, SIGBUS)
EXC_CRASH (SIGABRT)
Uncaught exceptions
Assertions
Watchdog timeouts
Stack overflow

Usage

Use when:

App crashes during testing
Need to analyze user crash reports
Debugging difficult-to-reproduce crashes
Tracking crash patterns
Preparing crash reports for issues

Output Format

Crash Summary
-------------
Process: PaleoRose
Bundle ID: com.example.paleorose
Version: 1.0.0
Date: 2025-11-08 20:30:15

Crash Type: EXC_BAD_ACCESS (SIGSEGV)
Exception: KERN_INVALID_ADDRESS at 0x0000000000000000

Crashed Thread: 0 (Main Thread)

Stack Trace:
  0  PaleoRose  0x10045a123 -[TableListController tableView:objectValueFor:row:] + 123
  1  AppKit     0x7fff2b3c4567 -[NSTableView _sendDataSourceValue] + 234
  2  AppKit     0x7fff2b3c4890 -[NSTableView reloadData] + 567

Probable Cause: Null pointer dereference in tableNames array access
Recommendation: Add nil check before accessing tableNames[row]