[hatari-devel] Debugger breakpoints for Hatari variables too?

[Kåre Andersen]

On Sun, Aug 2, 2009 at 9:18 PM, Eero Tamminen<eerot at users.berlios.de> wrote:
> 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).

What would be utterly perfect (and is already available in STEem debug
build) would be the ability to stop at a specific cycle within a
frame(that is, PC relative to the current VBL/HBL in cycles), and to
be able to set new breakpoints relative to the current one - in bytes
from PC _or_ in cycles/NOPs from PC....

This would make debugging synclock code a dream...

Oh, and about 32/64bit ints - why not just use SDLs builtin Uint32/Sint32 types?

/Kåre