- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
07528 | Crash/Freeze | Critical (emulation) | Always | Dec 23, 2019, 12:07 | Dec 23, 2019, 13:34 |
Tester | Yonah | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | Resolution | Fixed | OS | Windows 10 (64-bit) | |
Status [?] | Resolved | Driver | |||
Version | 0.216 | Fixed in Version | 0.217 | Build | 64-bit |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 07528: assorted drivers: Can't start emulation due to ACCESS VIOLATION when using -verbose | ||||
Description |
Exception at EIP=0000000000000002 (+0x0002): ACCESS VIOLATION While attempting to write memory at 0000000000000002 |
||||
Steps To Reproduce | |||||
Additional Information |
The issue comes about with an error with GCC 8.3.0. Using another version, such as the current top facing 9.2.0 does not have this issue. http://www.mameworld.info/ubbthreads/showthreaded.php?&Number=384425 |
||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | assorted drivers | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
4
No.17292
Yonah Tester
Dec 23, 2019, 12:20
|
Problem resolved when roms are run in a fresh separate install folder of MAME 0.216. There errors I'm getting happened after I overwrote the older files in a previous MAME folder as I've always done before. |
---|---|
No.17293
Yonah Tester
Dec 23, 2019, 12:54
|
Found the problem. I only get this crash with some drivers (dec0, midyunit, atarisy1) when I have "verbose 1" in mame.ini or star MAME with -verbose |
No.17295
Tafoid Administrator
Dec 23, 2019, 12:58
edited on: Dec 23, 2019, 13:33 |
-verbose was known to have issues with certain sets, yes, which was fixed shortly after release. |
No.17296
Yonah Tester
Dec 23, 2019, 13:02
|
Alright, I've disabled it for now. Thanks. |