[hatari-devel] Exception debugging & breakpoints
Laurent Sallafranque
laurent.sallafranque at free.fr
Sat Jun 11 11:34:35 CEST 2011
Hi,
I full agree with you Eero, there are still things to do for newcpu.
I would also add :
- update winuae's core to it's latest version (the one I used is about 1
year old now)
I know a regression with the new core (already mentionned in another
thread).
Some programs are looping forever in do_specialties()
Regards
Laurent
Le 10/06/2011 22:09, Eero Tamminen a écrit :
> Hi,
>
> On perjantai 10 kesäkuu 2011, Eero Tamminen wrote:
>> Hm. Maybe best is to call debugger in Exception() just to pass
>> the above exception information to the debugger, but let the actual
>> debugger invokation happen at the normal place.
> I looked into WinUAE code too, and it seems still to be missing all
> Exception debugging support (like discussed in earlier "68030 Debug
> mode and new CPU" thread). On double bus error, it e.g. uae_reset()
> instead of notifying user first and rebooting after "OK" like old
> UAE core does.
>
> -> I think doc/todo.txt should have a section on features
> missing from WinAUE core.
>
> Is WinUAE core missing anything specific besides:
> * Exception debugging support
> * Fixing& documenting cmdline options for selecting prefetch etc
> (and adding them to GUI)
> * Enabling/fixing MMU support
> That should be added to todo.txt?
> ?
>
>
> Btw. Nicolas, what's your current schedule for Hatari v1.5 release?
>
> I.e. would it be OK if I add history& old-UAE Exception support to
> debugger before it (will need also doc update before release)?
>
>
> - Eero
> _______________________________________________
> hatari-devel mailing list
> hatari-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/hatari-devel
>
More information about the hatari-devel
mailing list