Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06638 Crash/Freeze Critical (emulator) Always 23 days ago 14 days ago
Tester Tafoid View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows Vista/7/8 (64-bit)
Status [?] Confirmed Driver
Version 0.188 Fixed in Version Build
Summary 06638: Exception when using -debug
Description The following sets/drivers exception when using -debug either before the debug window starts or as soon as you begin execution:
Sets using HD44801 in champbas.cpp (exctsccr, talbot, champbasj, etc)
Exception at EIP=00000000035942b0 (crc32_little+0x0080): ACCESS VIOLATION

--
Sets using HD44801 in equites.cpp (equites, gekisou, hvoltage, etc)
Exception at EIP=00000000035942b0 (crc32_little+0x0080): ACCESS VIOLATION

--
gamt16b - gamtor.cpp
Exception at EIP=00000000033aef37 (d68000_ori_8()+0x0027): ACCESS VIOLATION
--
All sets in hh_hmcs40.cpp
Exception at EIP=0000000003594376 (crc32_little+0x0146): ACCESS VIOLATION

--
speeddrv - igspc.cpp
Exception at EIP=000000000338ebb4 (i386_dasm_one(std::ostream&, unsigned int, unsigned char const*, int)+0x00c4): ACCESS VIOLATION
--
instruct - instruct.cpp
Exception at EIP=00000000033f6fd3 (ADR(int)+0x0033): ACCESS VIOLATION
--
All sets in shougi.cpp
Exception at EIP=00000000035942b0 (crc32_little+0x0080): ACCESS VIOLATION

Steps To Reproduce
Additional Information Likely regression commit:
https://github.com/mamedev/mame/commit/8d2a1d4268e86fc20d9807df9dfe00ea1fb66b37
Flags
Regression Version 0.188
Affected Sets / Systems
Attached Files
 
Relationships
There are no relationsihp linked to this issue.
Notes
4
User avatar
No.14075
Robbbert
Developer
18 days ago
edited on: 18 days ago
Tested, they all work for me except:

gamt16b: crash as per the report

speeddrv: i don't have the chd

shougi2.cpp doesn't exist.

User avatar
No.14081
Tafoid
Administrator
17 days ago
instruct as well still crashes when using -debug
User avatar
No.14087
Osso
Developer
16 days ago
gamt16b: the cpu core doesn't seem to cope well with the first program ROM being a NO_DUMP.
Changing ROMREGION_ERASEFF to ROMREGION_ERASE00 avoids the crash, but it isn't a real fix.
User avatar
No.14088
Robbbert
Developer
14 days ago
Instruct works fine here with -debug. (32-bit build)