07295: midnrun and clones: Crash when F3 pressed

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07295	Crash/Freeze	Critical (emulator)	Always	Apr 24, 2019, 01:55	1 hour ago

Tester	Robbbert	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Open	OS	Windows Vista/7/8 (64-bit)
Status [?]	Confirmed			Driver	konami/zr107.cpp
Version	0.208	Fixed in Version		Build
		Fixed in Git Commit		Github Pull Request #

Summary	07295: midnrun and clones: Crash when F3 pressed
Description	The game bombs out when F3 is pressed.
Steps To Reproduce	Start the game. Wait for it to get into the attract mode. Press F3. It crashes. 64-bit: no message, mame just exits unexpectedly. 32-bit: terminate called after throwing an instance of 'emu_fatalerror' what(): std::exception This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
Additional Information
Github Commit

Flags
Regression Version	0.175
Affected Sets / Systems	midnrun and clones

Attached Files	0000.png (39,424 bytes) Apr 26, 2019, 01:34 Uploaded by Hydreigon
	jetwave.png (19,243 bytes) Apr 26, 2019, 01:41 Uploaded by Hydreigon
	slrasslt.png (35,793 bytes) Apr 26, 2019, 01:42 Uploaded by Hydreigon

No.16364 Tafoid Administrator Apr 24, 2019, 02:09	Version testing shows 0.174 works, 0.175 crashes. Added regression version
No.16365 Robbbert Moderator Apr 24, 2019, 07:04	ARCADE build has its own issue of the watchdog going off, and causing a reset, thereby creating this crash. The 64-bit version reported: "Fatal error: SHARC: PCStack underflow". It might be helpful as it's the only message to say anything of use so far.
No.16366 Osso Moderator Apr 24, 2019, 07:05	This only happens with the DRC enabled.
No.16367 Robbbert Moderator Apr 24, 2019, 07:11	More testing revealed that the -nodrc switch gets around the issue. The game works normally from what I can see.
No.16380 Hydreigon Tester Apr 25, 2019, 15:40 edited on: Apr 26, 2019, 01:44	As a matter of fact, this happens in all sets in zr107 and gticlub except Hang Pilot. Uploaded some screenshots of what happens before the crash.
No.22850 Robbbert Moderator Jan 17, 2025, 11:42 edited on: Jan 19, 2025, 14:31	Just checked again. First time run, press F3, it quit to the command line without a message. But subsequent tests worked, even after deleting game files. Weird. Perhaps an uninitialised variable.
No.22862 Osso Moderator Jan 19, 2025, 09:09	on 64 bit I still get the Fatal error: SHARC: PCStack underflow when it quits.
No.24117 cuavas Administrator 16 hours ago	9c1eb3d13371a108eaa11fe0c31396bc321a33a5 causes it to happen for me on initial start, not just after a soft reset (Windows AArch64 debug build). If you start it with the debugger and let it run through the RAM and ROM tests, then step one frame at a time (F8 or Run until Next VBLANK), the last frame number you'll see before it hits the fatal error is 1082. Possibly something not initialised properly on reset for the recompiler?
No.24118 JimCarlTay Senior Tester 1 hour ago	Fixed in midnrun as of commit d6388c3. Other observations as of that commit: - gticlub and thunderh: F3 reset leads to some failing entries in the ROM/RAM check - hangplt: Now freezes after F3 reset - jetwave: Crashes after soft reset with same fatal error as slrasslt - slrasslt: Freezes during lever initialization at first boot, soft reset with F3 on subsequent boots leads to fatal error ("Fatal error: SHARC: Status Stack overflow") - windheat: Crashes after soft reset without warning Overall, it still appears that the SHARC recompiler still needs more work.