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

[Eero Tamminen]

Hi,

On Sunday 09 August 2009, npomarede at corp.free.fr wrote:
> I see a little possible improvement, but perhaps it's too specialized to
> be added : when using LineCycles as a beakpoint var, we should warn the
> user if the value is not a multiple of 4, as LineCycles so far can only
> be this way. There could be a ValidMask, and we would warn
>  	if ( value != value & ValidMask )
>
> Some variables could also have a mix/max limit, but this is harder to
> determine as it can change dynamically (nHBLs depending on freq 50/60). I
> think it's easier for the user to pay attention to the range, than to
> check if a value is multiple of 4 for example.

This is a bit too complicated as it requires parsing the whole expression,
not just the stuff on the variable's side of the condition expression.

I added just a comment about LineCycles limitation to the breakcond.c help.


> One remark, from my use, I think it's better to avoid scrolling and to
> display as little lines as possible in the terminal, so I think it could
>
> be more efficient when using 'v' to replace :
> > v 127
...
> Value '127' is : %1111111 (bin)  #127 (dec)  $7f (hex)
>
> That is, everything on one single line.

Done.


> > Do you have a proposal patch for debugui.c?  I'm not sure what it
> > should look like...
>
> Sthg like :
>
> PC=xx  VBL=xx FrameCycles=xx HBL=xx LineCycles=xx

Done.  Although I used CPU=xx, DSP=xx as both have their own PC.


> Rather simple, but I think in the end people that use the debugger will
> care for immediate visibility of the values, so avoiding "words" seems
> more efficient.

I calso hanged the Debugger welcome message about help & continuing to
be shown only on the first debugger invocation.


	- Eero