Diagnose memory faults and allocation failures in the Breenix kernel.
npx skills add https://github.com/ryanbreen/breenix --skill memory-debugging
Please help me install this Agent Skill. Skill: memory-debugging Source: https://github.com/ryanbreen/breenix/tree/main/breenix-memory-debugging Command: npx skills add https://github.com/ryanbreen/breenix --skill memory-debugging
Memory-related bugs like page faults, double faults, and heap corruption are among the most challenging and critical issues in kernel development. This Skill provides a systematic approach to diagnose and resolve these complex memory problems, ensuring kernel stability and preventing system crashes.
PAGE FAULT during a system call. Use this Skill to decode the error code, determine if it's a read/write access or a user/kernel mode issue, and systematically investigate the page table mappings and kernel stack configuration to find and fix the underlying memory bug.log::debug!("CHECKPOINT: Before page table operation"); page_table.map_to(page, frame, flags, allocator)?; log::debug!("CHECKPOINT: After page table operation");
High-intent search queries and answers about installing and using this skill.
Page fault error codes are decoded bit-by-bit to identify the access type and memory state. Bit 0 indicates page presence, bit 1 shows read/write access, and bit 2 reveals user/kernel mode. Analyzing these bits pinpoints whether the fault stems from unmapped memory, protection violations, or mode mismatches, guiding your investigation into page table mappings and kernel stack configuration.
Double faults occur when an exception handler itself triggers an exception, often due to stack overflow, invalid page table entries, or corrupted kernel state. Systematic diagnosis requires logging checkpoints around page table operations, stack allocation, and frame allocator calls to isolate which memory subsystem failed and cascade the fault.
Yes. Heap corruption and frame allocation failures are diagnosed through integrated logging hooks that expose allocator state, track allocation/deallocation patterns, and introspect memory subsystem internals. Checkpoint logging before and after allocator operations narrows down where corruption or exhaustion occurs.
Troubleshooting kernel stack overflows and virtual memory mapping errors requires state introspection of the kernel stack allocator and page table subsystems. Use checkpoint logging to trace memory operations, inspect frame availability, validate virtual-to-physical mappings, and identify protection flag misconfigurations causing faults.
Integrated logging hooks are essential for effective memory diagnosis. They enable checkpoint logging around critical operations, state introspection of frame allocators and page tables, and actionable diagnostics. Without logging infrastructure, isolating memory defects in page faults, allocator failures, and stack issues becomes significantly harder.
Prevention requires proactive diagnosis and remediation of memory defects before they cascade into system crashes. Use this Skill to decode fault conditions, introspect allocator and page table state, and identify root causes of page faults, double faults, and allocation failures. Systematic investigation of early-stage symptoms prevents cascading failures.
AJBcodingGenerate memory-safe C code with malloc, calloc, realloc, and free.
openeuler-mirrorDiagnose memory leaks in Linux processes and kernel subsystems from memory metrics.
kiddyboots216Gather Linux OS, kernel, CPU, memory, uptime, and health metrics.
dyyounggCapture CUDA crash boundaries and tensor metadata via kernel API logging in SGLang.