Re: [hatari-devel] Lockup & Sidetracked demos |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Lockup & Sidetracked demos
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Mon, 7 Dec 2020 07:23:10 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1607322191; bh=ba6/dCQBe+bpJh/p2ao9ZelL+Zz/YPdbXwuNfLeF2Lo=; h=Subject:To:From:Date:From; b=OuQrQeDtth6PRYf0lIvHoR/6fgJeJ+zMh2xybVLUY2521iqQU5RRv6zfZgxfTzfk4 roCsoPd1MGhqsUPnXtLyYHHpFA0ZmnNuLmJVTGLvdUD65s6JtUz78EkIqs8p5t4YtN /LSxG8GZvZogK6W4rEx5kAIwSAwOP8tPjDjqcvRTJeXarDf64RuKA4JVyHQdCBPl1K bwplX91UK+qUFBmnNOzkrnHINEop7B0xgo4FHKqLIcghLTRnywmuCPs3r/LGKWWAHh L8cBbx1A6ciFR2kxl6gmVjBf4hSziDSKH2vtd41wiLAwY3wUwwVNQwekPCq3+YXIBV 2jS2G52ZJf78A==
> On 12/6/20 9:47 PM, Eero Tamminen wrote:
>> Sorry, I didn't notice this earlier as it wasn't
>> to hatari-devel (I've now changed my mailing list
>> rules to check also subject line, not just to/cc).
>>
>> On 12/6/20 8:00 PM, Laurent Sallafranque wrote:
>>> You can try to download this program again.
>>>
>>> It looks like the same problem I had with Fun industries demo (it didn't
>>> work with all my versions of hatari, but I was pretty sure it was a
>>> working demo). I've downloaded another version and now it works.
>>
>> I set all my Atari related files as read-only, unless program doesn't work
>> when that's done
>> (GEMDOS HD trace shows file whether files are
>> being opened as writable).
>>
>> That way programs can't accidentally corrupt their
>> files.
>>
>>
>> I also keep the original zip files around so that
>> I can verify files against the original files afterwards. None of
>> Sidetracked demo files have
>> changed/corrupted.
>>
>>
>> I just noticed that tracing shows following just
>> before it panics:
>> ----------------------------
>> ...
>> XBIOS 0x6D Dsp_ExecProg(0x2BE26, 0x2DD, 0x8001)
>>
>> GEMDOS opcode invoked outside of cartridge space
>>
>> Panic: Illegal Instruction
>> ----------------------------
That likely just means that the program executed garbage in the memory and
then crashed.
You'd need to step through the execution to see where it is exactly going
wrong (e.g. by comparing the run to a working one from HD image), but I'd
assume that it fails already earlier and that the "GEMDOS" opcode was really
just junk in memory that got executed by accident.
Thomas