Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07357 Crash/Freeze Critical (emulation) Always Jun 12, 2019, 01:18 Jun 28, 2019, 05:19
Tester Hydreigon View Status Public Platform MAME (Official Binary)
Assigned To AJR Resolution Fixed OS Windows 10 (64-bit)
Status [?] Resolved Driver
Version 0.210 Fixed in Version 0.212 Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 07357: All sets in taitojc.cpp: Reset loop after startup screen
Description The games will watchdog reset right after the startup screen completes in an infinite loop. All games would at least start up ingame in earlier versions (last tested with 0.201).

Tested with sidebs2 and dangcurv.
Steps To Reproduce
Additional Information
Github Commit
Regression Version 0.210
Affected Sets / Systems All sets in taitojc.cpp
Attached Files
There are no relationship linked to this issue.
User avatar
Jun 12, 2019, 01:33
edited on: Jun 27, 2019, 15:32
Link to (incorrect) commit removed per Tafoid's statement.
User avatar
Jun 12, 2019, 02:21
Your assumption is incorrect, unfortunately. My research shows it works in 0.209 (tested dendego), so your commit linked would have already happened.
Actual breakage seems to stem, in testing, around the big core M68000 reconstruction:

Unless for some reason there are multiple issues, I only chose one set because you've claimed "all sets in".
User avatar
Jun 12, 2019, 13:15
I updated my report stating the two games I tested that did this behavior. I'm kind of curious if other games that used an m68k cpu in different drivers broke from the big rewrite?
User avatar
Jun 12, 2019, 13:51
I'd like to hope most issues were caught in regression testing shortly after the initial commit. That's my main task for MAME - performing all sorts of regression testing largely looking for changes of video/audio behavior of the first 10 seconds of an emulated run where most issues tend to pop up, logging snapshot and wavdata hashes for comparisons to previous tests. Sadly, stuff like this which is longer into the emulation can only be found through manual checking.
User avatar
Jun 27, 2019, 20:30
The point at which dangcurv runs off the rails (not dendego's rails) in 0.210 and later appears to be the CINVA DATA instruction at PC = 00082724. This results in an F-line exception which shouldn't occur here.