// Compare memory regions between generic and JIT memory dumps to find divergences
Check that aarch64 JIT interpreter functions match generic CPU behavior
Analyze jitc.log to find JIT compilation issues — fragment gaps, branch overflow, bad codegen
Analyze a kernel Oops from the printk buffer in a PearPC memory dump
Analyze the JIT dispatch trace to diagnose boot stalls or crashes
Extract and display the Linux kernel printk ring buffer from a PearPC memory dump
| name | compare-dumps |
| description | Compare memory regions between generic and JIT memory dumps to find divergences |
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]
# Search for a 32-bit value:
python3 scripts/debug/memdump.py find memdump_jit.bin HEXVALUE
# Scan a range for differences:
python3 scripts/debug/compare_dumps.py memdump_generic.bin memdump_jit.bin --scan PA_START PA_END
Kernel VA to PA: PA = VA - 0xC0000000. All addresses in hex.