check-trace

Parses jitc_trace.log to identify boot stalls and crashes from JIT dispatch patterns.

438|75|Updated Jan 11, 2015
One-click install
npx skills add https://github.com/sebastianbiallas/pearpc --skill check-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-trace
Source: https://github.com/sebastianbiallas/pearpc/tree/main/.claude/skills/check-trace
Command: npx skills add https://github.com/sebastianbiallas/pearpc --skill check-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes JIT dispatch traces to diagnose boot stalls or crashes in the emulator by interpreting jitc_trace.log and highlighting common failure patterns.

Core Features & Use Cases

  • Pattern-aware analysis of jitc_trace.log to detect idle loops, repeated PC sequences, and abnormal dispatches
  • Failure-mode identification for DSI, DEC interrupts, and syscalls based on PA/EA traces
  • Targeted debugging workflows by filtering by address or instruction, counting occurrences, and verifying DEC timer and WATCH events
  • Developer-oriented diagnostics for PowerPC JIT dispatch behavior

Quick Start

Run the analysis against jitc_trace.log and, if desired, provide an argument to filter for a specific pattern at the JIT dispatch level.

Frequently Asked Questions about check-trace

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

FAQPage Schema
How do I diagnose PowerPC emulator boot stalls using a JIT trace log?

You can diagnose boot stalls by parsing jitc_trace.log to detect idle loops, repeated PC sequences, and abnormal dispatches. This analysis highlights common failure patterns by inspecting dispatches and addresses.

What is the best way to detect missed timer interrupts in a JIT dispatch trace?

Detecting missed timer interrupts involves verifying DEC timer and WATCH events within jitc_trace.log. By filtering dispatches and counting occurrences, you can isolate abnormal JIT dispatch behavior causing crashes.

How do I filter jitc_trace.log by address to debug unexpected syscalls?

Filter jitc_trace.log by a specific address or instruction to debug unexpected syscalls. Using common shell utilities like bash, grep, and awk, you can count occurrences and isolate targeted dispatches.

Can I use shell utilities to identify DSI interrupts in jitc_trace.log?

Yes, you can use shell utilities like bash, grep, and awk to identify DSI interrupts in jitc_trace.log. These tools count occurrences, filter by address, and verify timer and WATCH events for debugging.

Does this JIT trace analysis require any external dependencies or packages?

No external dependencies are required. The JIT trace analysis relies entirely on common shell utilities such as bash, grep, and awk already available in standard developer environments to parse the log.