Re: [hatari-devel] Bug in Hatari 2.0

["Roger Burrows" <anodyne@xxxxxxxxxxxx>]

On 28 Jan 2018 at 19:11, Nicolas Pomarède wrote:

> Le 28/01/2018 à 17:23, Thomas Huth a écrit :
> > Am Sat, 27 Jan 2018 16:17:58 -0500
> > schrieb "Roger Burrows" <anodyne@xxxxxxxxxxxx>:
> >
> >> On 27 Jan 2018 at 12:52, Thomas Huth wrote:
> >
> > Thanks! With that config file, I can reproduce the crash even with the
> > latest version from the Mercurial repo. Seems like the problem is when
> > you specify an FPU together with the GEMDOS hard disk. I was able to
> > reproduce it with this minimal config file, too:
> >
> > [HardDisk]
> > bUseHardDiskDirectory = TRUE
> > szHardDiskDirectory = /tmp/hatari/gemdos.drv
> >
> > [ROM]
> > szTosImageFileName = /tmp/hatari/etos512k.img
> >
> > [System]
> > n_FPUType = 68882
> >
> > The "n_FPUType = 68882" seems to trigger a re-initialization of the CPU
> > tables (even though it likely should not do that) as soon as you press
> > the OK button in the GUI. I guess that somehow kills the special
> > GEMDOS HD opcodes of Hatari, so that you finally run into a crash.
> > Unfortunately, I currently don't have much time for further debugging
> > (for the next 1.5 weeks) ... so either somebody else needs to have a
> > closer look or this has to wait a little bit.
> >
>
> Hi
>
> when I try this with my config, it just prints :
> FPU is not supported in 68000/010 configurations.
>
> Does this need a specific CPU or machine type to see the problem ?
>
I've just played around with this some more.  With the above minimal config,
here's how to reproduce this:
1. Create hatari.cfg with just the above lines
2. At the shell, just type "hatari"
3. You see the usual bus error messages on the terminal screen
4. When the EmuTOS boot screen appears, press F12
5. When the GUI appears, click the OK button
6. You get a few more messages on the terminal screen, including:
	FPU is not supported ...
	Building CPU ...
	CPU=68000 ...
	cpu change 1
Then:
	Illegal instruction 0008 at 00FA002A -> 00E008F0
	Illegal instruction 0008 at 00FA002A -> 00E008F0
7. Finally EmuTOS crashes with a panic message

This is not exactly the same as my problem (in my case, the F12-followed-by-OK
sequence caused a problem whenever it was used) but it seems like the same root
cause since the final messages from Hatari were the same.

Roger