[hatari-devel] Hatari v1.3 release issues

Eero Tamminen eerot at users.berlios.de
Sat Aug 15 17:27:28 CEST 2009


Hi,

On Saturday 15 August 2009, Thomas Huth wrote:
> > Before release, I'd like still do the couple of trivial things for the
> > debugger you asked for, that should be done by tomorrow.
>
> Ok, then I'll wait til tomorrow with the new release.

Done, if the changes are acceptable.


> > I also remove the -D option Pause/AltGr+Pause switching as it's
> > confusing.
>
> Right, that's not required anymore now that there's a dedicated
> shortcut key for the debugger.

This (key switching removal) is now done too.

Note that removal of the whole -D option wouldn't be so nice.  One might
want to debug exceptions right after boot or loading a memsaved emulation
state and then it could be a bit a hit and miss whether one has time to
press AltGr+Pause to invoke debugger...

(I mean, the option would then need to be replaced with config option and
separate debugger command which doesn't sound any better.)


> > 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:
> > ------
> > 	Double bus error detected.
> > 	        Emulation halted.
> > 	            [ Reset ]
> > -------
> > What do you think?
>
> 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? :-))

Other alternative would be just to show something like "HALTED" in
the statusbar.  So that the user knows to reset the emulation himself.


> Do you know any programs causing double bus errors?

Try for example starting "Punish your machine" with 512kB RAM and EmuTOS.

Hatari tells just in the console that it halted the emulation.


	- Eero



More information about the hatari-devel mailing list