analyze-oops

To analyze a kernel Oops from a PearPC memory dump, provide the dump file to the tool to extract the Oops, decode pt_regs, and disassemble around NIP and LR. This generates a structured diagnostic report pinpointing faulting addresses.

Decoding pt_regs during kernel Oops debugging reveals the exact faulting context of the crash. The skill decodes these registers from the memory dump to help correlate addresses and understand the processor state at the time of the fault.

Yes, you can use this tool to disassemble around NIP and LR to locate the code path leading to the crash. It correlates these addresses from the memory dump to pinpoint the exact instructions triggered during the kernel Oops.

Yes, the memory dump analysis validates NIP against known address spaces such as kernel, PROM, and PCI. This validation step ensures the faulting address is correctly categorized before generating the final structured diagnostic report.

Yes, you need the included Python scripts located under scripts/debug to parse memdumps for kernel Oops extraction. These scripts automate translating virtual addresses to physical addresses and produce the structured diagnostic report.