Re: [hatari-devel] Error dialog needs cold reset button |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Error dialog needs cold reset button
- From: David Savinkoff <dsavnkff@xxxxxxxxx>
- Date: Wed, 13 May 2015 11:32:38 -0600 (MDT)
- Thread-index: qzA75fp8/TrO/SAlzHq0c4asHvEpCg==
- Thread-topic: Error dialog needs cold reset button
----- Nicolas Pomarède wrote:
> Le 16/03/2015 00:19, Nicolas Pomarède a écrit :
>
> > I don't think it gives problem to call Reset() outside of the main input
> > loop (although I didn't try it). But we should call Reset_Warm() in
> > fact, as on a real STF you would likely press the reset button, which
> > does a warm, not cold, reset.
> >
> > You can modify old cpu core if you like, if it's OK I will add the
> > changes to WinUAE's cpu (which has a different/better "halt" state)
> >
> > Nicolas
>
> Hi
>
> back to this topic, I made some changse to handle the 'halt' state and
> display a dialog box in such case to let the user do a warm reset or
> call the debugger, instead of being locked in an endless loop.
>
> David, can you test with your case ?
>
> In my case, a way to trigger double bus/address error is to run tos3.06
> in tt mode, but with a 68000 and 24 bit addresssing (instead of the 32
> required), which is not compatible.
> eg :
>
> ./hatari --tos tos306fr.img --machine tt
>
> This will crash during the RAM detection and show the new dialog.
>
> Apply the following patch to test with old cpu core ; if it works for
> you, I will add a similar dialog to the WinUAE cpu core.
>
>
> Nicolas
>
***************************************************
tested OK with hatari.5620 (problem first noted)
tested OK with hatari.5710 (most recent version)
Reset works well for the [OK} button.
I noticed that Hatari leaves full Screen mode when
the [Cancel] button is pressed to go to the debugger
terminal. Works well, but is there a problem if the
debugger (readline library) isn't built ?
Leaving full screen mode is very important so that
you regain control of the desktop.
Note the halt.diff patch gives these compiler warnings:
[ 25%] Building C object src/uae-cpu/CMakeFiles/UaeCpu.dir/newcpu.c.o
hatari.5710/src/uae-cpu/newcpu.c: In function ‘m68k_reset’:
hatari.5710/src/uae-cpu/newcpu.c:1570: warning: implicit declaration of function ‘STMemory_WriteLong’
hatari.5710/src/uae-cpu/newcpu.c:1570: warning: implicit declaration of function ‘STMemory_ReadLong’
David Savinkoff
***************************************************