Re: [hatari-devel] Solved: Pure debugger, illegal opcodes, exceptions

[ Thread Index | Date Index | More Archives ]


I've just downloaded your patch, compiled and tested moongame.
The mouse still not move at all and I still get the illegal access message in the console.

Do you still have the following lines when starting hatari (newcore) ?

Exception 2 (0) at e02ce2 -> e02ce6!
A-Trap a000 at e010a0 (0x1b25c40)
A-Trap a00e at e010c0 (0x1b25c60)
A-Trap a000 at fa022c (0x1cc4dcc)
Exception 2 (0) at e01854 -> e01836!
Exception 2 (0) at e01854 -> e01836!
Exception 2 (0) at 20346 -> 20356!
A-Trap a000 at 20e02 (0xd459a2)

I haven't got them with old uae core.



Le 10/10/2012 22:48, Eero Tamminen a écrit :

I pushed a fix to repository.

Pure Debugger starts now fine with WinUAE.

I also noticed that X-moon game works fine with it now,
but I'm not sure was it because of this change.

(For some reason the game stops while one keeps
joypad fire button down which makes it pretty
annoying to play, but otherwise it works fine.)

	- Eero

On keskiviikko 10 lokakuu 2012, Nicolas Pomarède wrote:
Le 10/10/2012 18:16, Eero Tamminen a écrit :
	- Eero

[1] In this case maybe STMemory_ReadLong() which is e.g. used

      by the gemdos HD emulation.

yes, it should be this way, get_long is "interpreted" and should only be
used in emulation context not when you just want to peek a value to
print it in some logs.

See my comment in mfp.c in 2008/04/20 :)

"In the TRACE call in 'MFP_Exception', replace 'get_long' by
'STMemory_ReadLong' because 'get_long' produced a bus error
if we were not already in supervisor mode when the mfp exception
occured. This could cause bus error when restoring snapshot
of a gemdos program for example if trace mode was activated."

Mail converted by MHonArc 2.6.19+