Re: [hatari-devel] Debugger question

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

Just put whatever output you want to happen / see on breakpoint to
a debugger input file and use it with a a tracing breakpoint.

"regs" CPU command doesn't support showing single register value
either, but you can use "evaluate" command to show register values.

I.e. just put e.g. to "breakpoint.ini" file this:
	e d0

And then tell debugger to execute that on breakpoint without stopping:
	b <condition> :trace :quiet :file breakpoint.ini

If you e.g. want to see that on each VBL:
	b VBL!VBL :trace :quiet :file breakpoint.ini


(External breakpoint input files and "evaluate" command are more
verbose than tracing breakpoints for registers, address contents
and variables.  I hope that's not a problem.)


	- Eero

On 12/09/2015 08:30 PM, Laurent Sallafranque wrote:
> Thanks a lot Eero, but my question was about the 68030 registers : d0 in
> my case.
>
> Regs shows all the registers, but I'd like to see only one register each
> time I arrive at a certain address (to see how this register changes).
>
> I'll have a closer look at your answear anyway.
>
> Regards
>
> Laurent
>
>
>
> Le 09/12/2015 19:13, Eero Tamminen a écrit :
> > Hi,
> >
> > (Sorry for late reply, my ISP SMTP server has some problems.)
> >
> > On 12/04/2015 12:12 PM, laurent.sallafranque@xxxxxxx wrote:
> > > I'd like to see the content of a specific register into the console
> > > without breaking while my code runs.
> > >
> > > I mean something like :
> > >
> > > b pc=$xxxxxx : trace : lock
> > >
> > > with lock = something like
> > >
> > > lock reg d0
> > >
> > > Is there a way to do this ?
> >
> > You can print all registers with:
> >     lock dspregs
> >     b <condition> :lock
> >
> > (lock option implicitly enables tracing.)
> >
> >
> > But I actually prefer just putting into file anything
> > I want to get done on breakpoint, and then using:
> >     b <condition> :trace :file <filename>
> >
> > As to showing just a single register value, while
> > CPU "r" (registers) command supports that, DSP "dr"
> > (dspregs) command currently supports just setting
> > value to given register or showing all registers'
> > values.
> >
> >
> > If you just want to see when register value changes,
> > use:
> >     b r0 ! r0 :trace :quiet
> >
> >
> >     - Eero