| Re: [hatari-devel] TT emulation crashes when there is no ACSI drive |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] TT emulation crashes when there is no ACSI drive
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Sun, 11 Aug 2019 11:49:49 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1565516989; s=strato-dkim-0002; d=seimet.de; h=In-Reply-To:References:Message-ID:Subject:To:From:Date: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=tz2uTIk9fmJomKHHHxY54aqFe68CfZxbS7YD02gSils=; b=axFVulejtctZ1P7NMVhZu6ZvUQsSHCQ0SHJocuZ0CFYN2+MSRbwWuaegDpf2CFKU5h NHEk7ihMf3zwngXBhEpInheyUXawMLSkcLHNehwf12x2Ee+IFb3N7UDft5ot/2tNtjI/ H+qz5+wsUNGhJAylB/vTc9+sZEPH33yp885fYYTylecagxJF8lxo/bZxfn1p7E7Z7bis tLGHO1pX6g3+t2ejcRAAjZZgVvJUJw0sB17wvOgURvZcTeikAxIy0DaQLhm3R2p5tNET k3ePdH4eV8w7Oeww+A2JcZeg7D7o2IPBxHPYHN0qI1dtt1xQhz+qGVFAoZs2Zneplndt w6bA==
Latest analysis says: My program crashes whenever the filename before
the extension has less than 4 characters. If I renaming it from 1.PRG to
NVDI.PRG for instance, it does not crash anymore.
There currently is no other program in my AUTO folder.
> Hi,
>
> Let me wait for the feedback on my stripped down binary first, see my
> last posting.
>
> Best regards
>
> Uwe
>
> > Uwe Seimet schrieb:
> >
> > > I'll try to identify the NF_SCSI call that triggers this.
> >
> > Thank you for investigating further. I still think knowing *how* the bus
> > error happened will help narrowing this down. Eero posted a detailed
> > guide how to capture a lot of information in his email from 06.08.2019,
> > 12:27.
> >
> > A less complicated but still helpful variant would be: Start Hatari in a
> > configuration which allows you to reproduce the crash but additionally
> > with the "-D" command line option. That will make Hatari break into the
> > debugger at each exception. You'll see several harmless bus errors
> > during TOS startup. At the first of such errors, when Hatari breaks into
> > the debugger, enter "history cpu 256" to enable the CPU history buffer.
> >
> > Keep entering "c" at the errors during startup until you hit the bus
> > error we're talking about. Execute the following debugger commands:
> > history 64
> > registers
> > ... and send the output to the list.
> >
> > Regards
> > Christian
> > --
> > Christian Zietz - CHZ-Soft - czietz@xxxxxxx
> > WWW: http://www.chzsoft.de/
> > PGP/GnuPG-Key-ID: 0x52CB97F66DA025CA / 0x6DA025CA
> >
> >
>
>