Re: [hatari-devel] New SYNC release. New Hatari bugs found ;)

[Troed Sångberg <troed@xxxxxxxxxxx>]

Well, my tracing was under Hatari (both v2.0 and latest dev at the time) and it was always those exact instructions. I did use TOS 3.06 Swedish though if we need to go hunting for differences in setup :) 

The loading of the intro is done by TOS from AUTO and will differ between (at least) TOS versions. The included color/mono binary is then depacked and moved to $c000 (always) from where it's executed. The crash happens sort of soon (but thousands of instructions) after that.

Indeed it's possible/likely that the same addresses have been executed from during the AUTO-loaded intro as is then reached from the $c000-based execution of the AS binary.

/Troed

-------- Original Message --------

Subject: Re: [hatari-devel] New SYNC release. New Hatari bugs found ;)

Local Time: December 3, 2017 8:35 PM

UTC Time: December 3, 2017 7:35 PM

From: npomarede@xxxxxxxxxxxx

To: hatari-devel@xxxxxxxxxxxxxxxxxxx, Troed Sångberg <troed@xxxxxxxxxxx>

Le 03/12/2017 à 20:21, Troed Sångberg a écrit :

In my original mail to the list I listed exactly which instructions I

traced and how the PC was advanced one word instead of two as indicated

by "next PC". It's repeatable to just set a breakpoint at that address.

I don't know enough about the 68030 caches to understand whether this

(PC advancing) is cache affected.

In my case, the program crashes on different opcodes that the ones you

saw, which would confirm it's a cache issue that could depend on how

program was loaded (maybe program is loaded at a different address under

Hatari than under real TT)

I'm still investigating, will try to get more infos tonight.

Nicolas