[hatari-devel] 68030 Debug mode and new CPU

Eero Tamminen oak at helsinkinet.fi
Tue Feb 15 22:05:45 CET 2011


Hi,

On tiistai 15 helmikuu 2011, Laurent Sallafranque wrote:
> > Which of the debug functions?
> > 
> > I took a quick look at the cpu/newcpu.c and the part that allows
> > breakpoints, disassembly tracing etc important stuff is there in
> > 
> > cpu/newcpu.c::do_specialties():
> >      if (regs.spcflags&  SPCFLAG_DEBUGGER)
> >      
> >                  DebugCpu_Check();
> > 
> > Doesn't that work?
> 
> I Think it doesn't.
> If I enter "r", it should show me the registers
> 
> But it only shows me the latest instruction :
> *****
> 
> >  r
> 
> 00E09CDC 2070 9800                MOVEA.L (A0, A1.L*1, $00) ==
> $00e4da50,A0 *

That's because you've commented out all the code in cpu/custom.c::f_out()
which is used (in the "r" command case) by cpu/newcpu.c::m68k_dumpstate() to
print out the information.  The disassembly stuff in WinAUE newcpu.c seems
to be using this f_out() stuff too.

You could add:
	#define f_out fprintf

to one of the headers, remove the f_out stuff from cpu/custom.c and replace
all "void *" args for functions calling f_out() with "FILE *".


	- Eero



More information about the hatari-devel mailing list