[hatari-devel] Hatari v1.3 release issues

[Thomas Huth]

On Sat, 15 Aug 2009 22:13:30 +0300
Eero Tamminen <eerot at users.berlios.de> wrote:

> On Saturday 15 August 2009, Eero Tamminen wrote:
> > > > I was also thinking that when catching of exceptions isn't
> > > > enabled, the double bus-error thingy should instead of halting
> > > > the emulation and making Hatari use 100% CPU, present user a
> > > > dialog:
> ...
> > > Sounds good, but maybe better postpone this until the new release
> > > has been done (since it requires changing the most internal CPU
> > > code a little bit - I don't want to have any regression bugs here
> > > right before a new release).
> >
> > Hm.  I thought this would be pretty easy.  Or is reseting the
> > emulator deep in the emulation what's risky?   (maybe you could
> > then do it after the release? :-))
> 
> I added a dialog notifying user about the halting (when DebugUI isn't
> called) which seems to work fine.  Reseting emulation after that can
> be done after the release.

Well, I rather thought about asserting SPCFLAG_BRK and then to
show/handle the dialog in m68000.c instead. In my eyes, the UAE CPU
code is some kind of "library" that shouldn't directly display an alert
dialog.
But ok, let's keep it this way for this release and think about a
cleaner solution (with reset button) later...

 Thomas