skills.rest
ryanbreen
ryanbreenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qemu-debug-session

Debug Breenix kernel under QEMU with monitors, logs, and CPU state inspection.

7|Updated Nov 21, 2015
Search Tags:#logging#qemu#gdb#monitor#kernel-debugging
One-click install
npx skills add https://github.com/ryanbreen/breenix --skill qemu-debug-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qemu-debug-session
Source: https://github.com/ryanbreen/breenix/tree/main/breenix-qemu-debug-session
Command: npx skills add https://github.com/ryanbreen/breenix --skill qemu-debug-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized workflow to debug the Breenix kernel via QEMU, including monitors, logs, and live inspection capabilities.

Core Features & Use Cases

  • Live inspection of CPU state, memory, and registers
  • Monitor access via TCP/stdio
  • Detailed logging and session management for reproducible debugging
  • Use Case: diagnose a boot failure by tracing interrupts, stepping into initialization, and capturing a repeatable log sequence

Quick Start

Set environment variables for logs and enable the monitor, then start QEMU with the Breenix binary and attach via monitor or GDB as needed.

Frequently Asked Questions about qemu-debug-session

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

FAQPage Schema
How do I debug a Breenix kernel running under QEMU?▼

Debugging Breenix under QEMU requires enabling the QEMU monitor and configuring GDB attachment. Set environment variables for logging, start QEMU with the Breenix binary, then connect via TCP monitor or stdio to inspect CPU state, memory, and registers live during execution.

Can I trace kernel interrupts and memory management issues in QEMU?▼

Yes. This Skill captures structured logs for interrupt handling, MMU activity, and page-table walks, enabling you to trace these events reproducibly. Configure debug flags to log specific kernel subsystems, then review captured sequences to diagnose faults.

What's the best way to diagnose a kernel boot failure with QEMU?▼

Trace the boot sequence by stepping through initialization with GDB, capturing interrupt logs, and inspecting CPU state at failure points. Live monitor access reveals register and memory state; structured logs create repeatable diagnostic records for boot-sequence problems.

How do I access the QEMU monitor while debugging a kernel?▼

The QEMU monitor is accessible via TCP or stdio, configured during Skill setup. Once connected, you can inspect and manipulate CPU state, memory, and registers interactively without stopping the debugger session.

Can I capture and replay kernel debug sessions for reproducibility?▼

Yes. Structured log capture records interrupt activity, MMU operations, boot diagnostics, and CPU state changes. Saved logs enable you to reproduce debugging sessions and share repeatable failure traces with collaborators.

Do I need GDB to use QEMU kernel debugging, or can I use the monitor alone?▼

Both approaches work. The QEMU monitor alone provides live inspection and command execution; adding GDB enables breakpoints and step-through debugging. Use monitor-only for quick state checks or GDB for detailed stepping and conditional breakpoints.

Related Skills

Explore More Software Engineering Skills→
ryanbreenryanbreen
7

github-workflow-authoring

Create and debug GitHub Actions pipelines for Breenix OS kernel CI/CD.

Community
Advanced
adriandarianadriandarian

trace-operations

Capture, replay, and export 3Lens traces via CLI for debugging and regression testing.

Community
Intermediate
ryanbreenryanbreen
7

gdb-chat

Automate interactive GDB debugging sessions for the Breenix kernel.

Community
Advanced
sebastianbiallassebastianbiallas
438

dump-printk

Extract kernel printk messages from a PearPC memory dump.

Community
Basic