sebastianbiallas

6 verified skills2,604 total stars

github.com/sebastianbiallas

analyze-jitc-log

Analyze jitc.log to find JIT compilation issues — fragment gaps, branch overflow, bad codegen

development434

analyze-oops

Analyze a kernel Oops from the printk buffer in a PearPC memory dump

tools434

--- name: compare-dumps description: Compare memory regions between generic and JIT memory dumps to find divergences allowed-tools: Bash, Read argument-hint: [subcommand] [args...] --- # Compare Memory Dumps Use `scripts/debug/memdump.py` subcommands: ``` # Read words at a PA (accepts kernel VA, auto-converts): python3 scripts/debug/memdump.py read memdump_jit.bin PA [count] # Diff two dumps at a PA: python3 scripts/debug/memdump.py diff memdump_generic.bin memdump_jit.bin PA [count] # Sear

tools434

.claude/skills/dump-printk

--- name: dump-printk description: Extract and display the Linux kernel printk ring buffer from a PearPC memory dump allowed-tools: Bash, Read argument-hint: [dump-file] [search-term] --- # Extract Kernel Printk Buffer Use `scripts/debug/memdump.py printk` to extract the printk ring buffer. ``` python3 scripts/debug/memdump.py printk $ARGUMENTS ``` If no arguments, use `memdump_jit.bin`. Report the last printk message, any Oops, and what boot stage was reached.

tools434