Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
02720 Crash/Freeze Critical (emulator) Always Dec 7, 2008, 08:54 Dec 9, 2008, 03:39
Tester Scagazza View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Unable to reproduce OS
Status [?] Closed Driver
Version 0.128u5 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 02720: cubeqst: cubeqst crash with acccess violation running with -debug
Description C:\MAME>mame cubeqst -debug

-----------------------------------------------------
Exception at EIP=0000000140595234: ACCESS VIOLATION
While attempting to read memory at 03931080
-----------------------------------------------------
RAX=0000000000008800 RBX=0000000001FBAD60 RCX=0000000001FBAF60 RDX=0000000000000
000
RSI=0000000004821080 RDI=0000000000000009 RBP=0000000000000000 RSP=000000000012F
9D0
 R8=0000000000000000 R9=0000000000000000 R10=00000000FFD29696 R11=0000000000000
000
R12=0000000000000110 R13=0000000000008800 R14=0000000004824080 R15=000000000390F
080

Cubeqst crash when you must choice your path on the cube, without -debug option mame simply quits no error messages.
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems cubeqst
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
6
User avatar
No.03244
Scagazza
Tester
Dec 7, 2008, 11:23
Regression is 0.128u4, 0.128u3 works fine for me.
User avatar
No.03245
Fujix
Administrator
Dec 7, 2008, 11:57
It doesn't repro here with or without -debug, on 32-bit xp / 64-bit vista.
User avatar
No.03246
Scagazza
Tester
Dec 7, 2008, 12:26
On my build pressing the cube button (spacebar) causes mame to quit too.
User avatar
No.03250
Tafoid
Administrator
Dec 7, 2008, 16:57
There was an issue with the -cheat trigger in u4 - make sure you don't have that in your mame.ini as "cheat 1". I've tried and I cannot duplicate your report.
on 32-bit, Windows 2000.
User avatar
No.03251
Scagazza
Tester
Dec 7, 2008, 17:00
I have done some tests compiling at 64 bit with and without optimizations using MSVC and cubeqst crash; no problem with mingw32.
My compiler is MSVC 2008 SP1.
User avatar
No.03253
Tafoid
Administrator
Dec 7, 2008, 17:29
Scagazza,

Over time, you have reported quite a few "unique to you" problems in the past (problems which were never reproduced by others). You should really try to discuss your found bugs with some other MAME users you might know before posting a report here again. Just be aware that constantly having to validate your errors which end up not being reproducible by anyone is a lot of wasted effort. Please consider this a warning. While we all make mistakes and have posted bad reports - it has happened far too often for you. Future bad reports might force us to take away reporting status.

If you can, please reinstall from scratch your compilation system and build using the guidelines here:
http://mamedev.org/devwiki/index.php/Building_MAME_using_Microsoft_Visual_Studio_compilers
The only 'official' versions are Microsoft Visual Studio .NET 2003 and 2005 (according to MAMEDEV information). I know you said you used MSVC 2008, which might be the a source of some of your issues. As always, make sure you are building from only MAMEDEV.org sources, properly patched and built using only approved tools. Also, ensure that you are not carrying over object files from previous build - that will most assuredly cause unreproducible results. It might be worth seeing if someone else you know might be able to produce a 64-bit version for you to see if the same issues happen.