Hi,
On keskiviikko 06 kesäkuu 2012, Nicolas Pomarède wrote:
Le 05/06/2012 22:35, Eero Tamminen a écrit :
Even if Hatari wouldn't crash, it may be emulating things wrong
because at least wrong dmaRecord.frameCounter value can scribble
all over Hatari's own memory, or over the emulated memory.
I guess invalid dmaPlay.frameCounter values just cause invalid
reads i.e. crashes without memory corruption and the evil stuff
that can follow from that.
Well, so far I'm unfortunately very busy, at least not with enough time
to dig more precisely in the falcon sound part.The little spare time I
have at the moment will be used to release next Hatari version
(including any remaining bugs such as this one).
I'm afraid this will have to stay this way for now, unless someone else
wants to give it a look before next release.
Ok, I'll add that as item to todo.txt.
By the way, it could also be an error in emutos where sound addresses
would not be set correctly.
EmuTOS is still lacking most of XBios functions that appeared
with TOS v4; everything for DSP, sound matrix etc. That's
why things go wrong on the Atari side.
But the point is that regardless of how badly things go at Atari
side, Hatari itself shouldn't crash when Atari registers have
bogus values.
- Eero