Re: [hatari-devel] Hatari Falcon emulation segfault with EmuTOS |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
Hi,
On maanantai 20 helmikuu 2012, Laurent Sallafranque wrote:
> I haven't got this problem actaully with tos 4.02 fr and 68030 cycle
> exact.
>
> This demo is one of the timing sensitive ones.
>
> I've done many tests with it where I had the illegal DMA sound problem,
And segfault?
> but with the current timings, I haven't got it.
> (But the demo freezes while displaying the gouraud fruits).
Please try with latest EmuTOS (which doesn't implement the OS
DSP or sound matrix XBios functions):
http://sourceforge.net/projects/emutos/files/snapshots/CVS-20120219/
Emulator needs to be robust against badly working emulated programs.
- Eero
> I think it'll become better in time when I have some time to continue to
> add the correct falcon timings.
>
> Regards
>
> Laurent
>
> Le 19/02/2012 21:27, Eero Tamminen a écrit :
> > Hi,
> >
> > I got Hatari segfault both with new and old CPU cores when
> > trying to run EKO's system demo with latest EmuTOS snapshot.
> >
> > hatari --bios-intercept --trace xbios --fast-forward yes --tos
> > emutos-512k- CVS-20120208/etos512k.img --machine falcon
> > eko_syst.em/system.prg
> >
> > Autostart file 'C:\EMUDESK.INF' for 'SYSTEM.PRG' matched.
> > Autostart file removed.
> > XBIOS 89 (VgetMonitor)
> > A-Trap a00a at 3b7b0 (0x85f3870)
> > XBIOS 2 (Physbase)
> > XBIOS 88 VsetMode(0xffff)
> > XBIOS 88 VsetMode(0xffff)
> > XBIOS 130 (Soundcmd)
> > XBIOS 130 (Soundcmd)
> > XBIOS 130 (Soundcmd)
> > XBIOS 139 (Devconnect)
> > XBIOS 135 (Setinterrupt)
> > XBIOS 37 (Vsync)
> > XBIOS 130 (Soundcmd)
> > XBIOS 130 (Soundcmd)
> > XBIOS 130 (Soundcmd)
> > XBIOS 139 (Devconnect)
> > XBIOS 135 (Setinterrupt)
> > XBIOS 37 (Vsync)
> > XBIOS 37 (Vsync)
> > <longish wait>
> > crossbar DMA Play: Illegal buffer size (from 0x0fde14 to 0x0fdde8)
> > XBIOS 37 (Vsync)
> > XBIOS 109 (Dsp_ExecProg)
> > Segmentation fault
> >
> > With the old core the segfault happens a bit earlier after
> > the crossbar message.
> >
> >
> > Segfault happens also without fast-forward (or tracing), but it of
> > course takes then a long time to happens.
> >
> > - Eero