Re: [hatari-devel] tracing of cpu (dsp) registers

[ Thread Index | Date Index | More Archives ]


On 01/24/2018 05:06 AM, Miro Kropáček wrote:
I've found this old email while looking for it *again*:

On 27 January 2014 at 06:27, Eero Tamminen <oak@xxxxxxxxxxxxxx> wrote:
On sunnuntai 26 tammikuu 2014, Miro Kropáček wrote:
today I'm celebrating, for the first time I was able to actually debug
something with Hatari ;-) It's nearly perfect, I missed only one thing
and that is something like "trace cpuregs" so after each step I see all
the regs along with the next instruction

You can already do that with:
         lock registers

This works well. However what I am (and I guess I was too) looking for is
printing the content of CPU regs automatically -- same as I let run, say,
trace cpu_disasm, I'd like to let run "trace cpu_regs" and just let the app
crash -- so I will see what led to that path without inspecting each line
of code.

Just to verify, do you mean running "registers" command after
*each* executed CPU instruction?

	- Eero

Mail converted by MHonArc 2.6.19+