[hatari-devel] Debugger breakpoints for Hatari variables too?
Eero Tamminen
eerot at users.berlios.de
Sun Aug 2 21:18:11 CEST 2009
Hi,
On Friday 31 July 2009, npomarede at corp.free.fr wrote:
> By the way, there's a possibility that I think would be quite useful : to
> be able to use Hatari's variable as breakpoint condition.
>
> The 2 variables I'm thinking about for now are nVBLs and nHBL, as
> sometimes you know a problem will happen after a certain time, or only at
> a certain line, so doing something like :
>
> VBL=30 && HBL=263 && ( $ff820a ) = 0
>
> would be really cool.
>
> Certainly some other variables could be exported this way, with a simple
> table to associate a string to a pointer to that variable (we could
> assume it's always 'int' size).
Debugger already support 8, 16 & 32-bit variables, so that's not a problem.
> Would change the parser and the breakpoint evaluation function, so I'm
> not sure if it could be done before release (Eero ?)
I don't see why not. I just need a function that maps variable names to
their addresses & sizes and call that if name didn't match to a register.
First I'd like a bit more complete list of all the variables that you,
Thomas, Laurent etc would want to be available to the debugger though...
For the release this will support only global variables.
- Eero
(Maybe later there could be also accessor functions for non-globals
variables that this function could use. It doesn't make sense to make
globals from static variables just for the debugger.)
More information about the hatari-devel
mailing list