[hatari-devel] Execution history debugger command
Eero Tamminen
eerot at users.berlios.de
Fri Jun 10 00:14:42 CEST 2011
Hi,
I decided that the history thing should:
* Store only PC for DSP & CPU, but for everything,
not just breakpoint
* When being asked for history, show disassembly of
instructions on these PC addresses
This can be utilized in breakpoints by automatically showing
the instructions leading to the breakpoint being hit, with
something like this:
lock history 20
b <some condition> :trace :lock
This would, whenever given condition is hit, show the "locked"
information i.e. history of requested last 20 instructions and
then continue.
I can make it shoe that PC values/instructions that were shown by
previous breakpoint aren't repeated if breakpoint happens to hit more
often than at 20 instructions interval.
You can also ask more history in debugger and it will mark in
the output the places where breakpoints (or other debugger
entries) happened.
This will give with couple of extra code lines variables for
previous DSP & CPU PC variable values which can be used e.g. to
find out jumps to some location that aren't loop jumps:
b pc = <entry address> && PrevPcCpu ! <loop jump address>
- Eero
More information about the hatari-devel
mailing list