[hatari-devel] Exception debugging & breakpoints

[Nicolas Pomarède]

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?
> ?

Don't know, really didn't have time to look at winuae recently ; we 
might add a note about this, but I don't think explaining it in larger 
detail in the doc is necessary for now.
It would be sthg like "use uae's core for ST + full debugger and use 
Winuae's core for falcon only and no debugger"

>
> 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)?

Very soon I hope, maybe around june 17th. So I think we should not add 
new features now but fixes any current issue we can find.
Especially touching to cpu's core is always risky, so I would prefer we 
postpone those features after 1.5 is released.

Nicolas