[hatari-devel] dsp trace instr

[Eero Tamminen]

Hi,

On sunnuntai 20 maaliskuu 2011, Laurent Sallafranque wrote:
> Le 20/03/2011 12:05, Eero Tamminen a écrit :
>> ->  This information should be in Hatari manual debugging section,
>> 
>>     under its own DSP debugging subsection I think.
> 
> DSP trace is activated when you lauch hatari with option --trace
> dsp_disasm (or when you use this option in the debugger console).
> 
> DSP disasm is when you use dd addr in the debugger to disasm a part of
> DSP memory.

Ah, OK.  I added short comment of "trace dsp_disasm" to manual.

 
> With my latest patch, everything works well, also if you use both of
> them at the same time.
> 
> >> 2 questions :
> >> 
> >> - Do you think that trace dsp_registers and trace dsp_memory should be
> >> added to the debugguer or should they stay as DEFINES and
> >> recompilation in dsp_cpu code ?
> > 
> > How often they're needed compared to the normal disassembling?
> > 
> > Both add a check to speed-critical DSP function, but memory tracing
> > would need also switching an often used auxialiary function at
> > run-time.
> 
> I know I use them a lot when debugging (it's nice to have the
> instruction, and then the register and memory changes).
> But it would need to rewrite some more code (maybe in 1.5+ version) ?

Version after v1.5 sounds fine. :-)


> > For now all you can run from breakpoint is the trace command, rest of
> > the actions you unfortunately need to do from the debugger prompt
> > yourself.
> 
> OK.

I started adding ":file" option directly to conditional breakpoints, so that
each breakpoint can have different actions (debugger commands file)
associated with it and so that it doesn't need to be same commands that
get executed when entering the debugger...

(I will also rename ":info" breakpoint option to ":lock" as it refers to
information specified with the "lock" debugger command.)


	- Eero