[hatari-devel] bug: WinUAE CPU ignores debugger output log file

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

WinUAE CPU core integration to Hatari isn't complete,
e.g. register dumping doesn't respect the debugger
log file setting.

This ignores the log file given for dumping:
---------------
#ifdef WINUAE_FOR_HATARI
void m68k_dumpstate_file (FILE *f, uaecptr *nextpc)
{
        m68k_dumpstate_2 (m68k_getpc (), nextpc);
}
#endif
---------------

This redirects things uncoditionally to console:
---------------
	src/cpu/compat.h:#define console_out_f printf
---------------

I think console_out_f() should use the log file user selected.


As a result of this, Hatari UI throws an exception when
one opens the debugger window because debugger (register
dump) output file is empty.  To fix it, WinUAE CPU core
log output stuff should be handled properly.


	- Eero