qemu_session.py: the CPU snapshot also dumps the code at each PC
Eight words at the PC, by its address, name the function offline. The image loads where the firmware puts it, and the boot does not print that address. aarch64's monitor has no $pc, so the address is taken from the register line; checked on a real, paused QEMU. Test first: the snapshot test, 6 checks; the new one failed before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
@@ -0,0 +1,7 @@
|
||||
PASS: qemu_session.py has cpu_snapshot()
|
||||
PASS: a failed check asks the monitor for the registers three times
|
||||
PASS: and prints where the CPU is, each time
|
||||
PASS: and the code at the PC each time, by its address (the monitor has no $pc on aarch64)
|
||||
PASS: a passing check asks the monitor nothing
|
||||
PASS: a monitor that does not answer does not stop the run
|
||||
RESULT: PASS
|
||||
@@ -0,0 +1,7 @@
|
||||
PASS: qemu_session.py has cpu_snapshot()
|
||||
PASS: a failed check asks the monitor for the registers three times
|
||||
PASS: and prints where the CPU is, each time
|
||||
FAIL: and the code at the PC each time, to name the function offline (x /8wx $pc)
|
||||
PASS: a passing check asks the monitor nothing
|
||||
PASS: a monitor that does not answer does not stop the run
|
||||
RESULT: FAIL
|
||||
Reference in New Issue
Block a user