analyze-oops — Fehleranalyse PowerPC analyze-oops, pearpc, community, Fehleranalyse PowerPC, ide skills, Fehlerbehebung Windsurf, analyze-oops AI-Agent-Fähigkeit, Python-Debugging, PowerPC-Architektur

v1.0.0

Über diesen Skill

Perfekt für Debugging-Agents, die erweiterte Kernel-Oops-Analysefunktionen in PowerPC-Architektur-Emulatoren benötigen Analyze-oops ist ein Werkzeug, um Fehler in der PowerPC-Architektur zu analysieren

Funktionen

Fehlerextraktion mit scripts/debug/memdump.py
Dekodierung von pt_regs mit scripts/debug/memdump.py
Disassemblierung von Code um NIP und LR
Kompatibilität mit der PowerPC-Architektur
Integration mit Windsurf
Fehleranalyse mit Python

# Core Topics

sebastianbiallas sebastianbiallas
[429]
[74]
Updated: 3/23/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
43
Canonical Locale
en
Detected Body Locale
en

Perfekt für Debugging-Agents, die erweiterte Kernel-Oops-Analysefunktionen in PowerPC-Architektur-Emulatoren benötigen Analyze-oops ist ein Werkzeug, um Fehler in der PowerPC-Architektur zu analysieren

Warum diese Fähigkeit verwenden

Ermöglicht es den Agenten, Kernel-Oops mithilfe von Skripten wie memdump.py und disasm_ppc.py zu decodieren und zu disassemblieren, wodurch eine tiefere Analyse der Oops-Ausgabe und von pt_regs ermöglicht wird und sie nahtlos mit KI-Coding-Assistenten wie Claude Code und Cursor zusammenarbeiten können

Am besten geeignet für

Perfekt für Debugging-Agents, die erweiterte Kernel-Oops-Analysefunktionen in PowerPC-Architektur-Emulatoren benötigen

Handlungsfähige Anwendungsfälle for analyze-oops

Fehlerbehebung von Kernel-Oops in PowerPC-Architektur-Emulatoren wie PearPC
Extraktion und Analyse von Oops mit memdump.py
Disassemblierung um NIP und LR herum mit disasm_ppc.py

! Sicherheit & Einschränkungen

  • Benötigt Python 3
  • Begrenzt auf PowerPC-Architektur-Emulatoren
  • Benötigt Skripte wie memdump.py und disasm_ppc.py

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is analyze-oops?

Perfekt für Debugging-Agents, die erweiterte Kernel-Oops-Analysefunktionen in PowerPC-Architektur-Emulatoren benötigen Analyze-oops ist ein Werkzeug, um Fehler in der PowerPC-Architektur zu analysieren

How do I install analyze-oops?

Run the command: npx killer-skills add sebastianbiallas/pearpc. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for analyze-oops?

Key use cases include: Fehlerbehebung von Kernel-Oops in PowerPC-Architektur-Emulatoren wie PearPC, Extraktion und Analyse von Oops mit memdump.py, Disassemblierung um NIP und LR herum mit disasm_ppc.py.

Which IDEs are compatible with analyze-oops?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for analyze-oops?

Benötigt Python 3. Begrenzt auf PowerPC-Architektur-Emulatoren. Benötigt Skripte wie memdump.py und disasm_ppc.py.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add sebastianbiallas/pearpc. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use analyze-oops immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

analyze-oops

Install analyze-oops, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Analyze Kernel Oops

Use scripts/debug/memdump.py to extract and analyze the Oops.

Steps

  1. Extract the Oops:

    python3 scripts/debug/memdump.py oops ${ARGUMENTS:-memdump_jit.bin}
    
  2. Decode pt_regs (use the REGS address from the Oops output):

    python3 scripts/debug/memdump.py regs DUMP_FILE REGS_ADDRESS
    
  3. Disassemble around NIP and LR (convert VA to PA: PA = VA - 0xC0000000):

    python3 scripts/debug/disasm_ppc.py DUMP_FILE PA_OF_NIP 16
    python3 scripts/debug/disasm_ppc.py DUMP_FILE PA_OF_LR 16
    
  4. Search for the NIP value in both dumps:

    python3 scripts/debug/memdump.py find memdump_generic.bin NIP_VALUE
    python3 scripts/debug/memdump.py find memdump_jit.bin NIP_VALUE
    
  5. Check if NIP is a valid address:

    • 0xC0xxxxxx = kernel code
    • 0xBFxxxxxx = PROM virtual address (prom_mem_phys_to_virt)
    • 0xFDxxxxxx = PCI I/O space (not executable)

Report: exception type, faulting address, caller, what the code was trying to do.

Verwandte Fähigkeiten

Looking for an alternative to analyze-oops or another community skill for your workflow? Explore these related open-source skills.

Alle anzeigen

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
Künstliche Intelligenz

widget-generator

Logo of f
f

Erzeugen Sie anpassbare Widget-Plugins für das Prompts.Chat-Feed-System

149.6k
0
Künstliche Intelligenz

flags

Logo of vercel
vercel

Das React-Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensor und dynamische neuronale Netze in Python mit starker GPU-Beschleunigung

98.6k
0
Entwickler