Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
03464 Debugger Critical (emulator) Always Oct 5, 2009, 12:17 Sep 24, 2012, 13:58
Tester sronco View Status Public Platform MAME (Self-compiled)
Assigned To Firewave Resolution Fixed OS Windows Vista/7 (32-bit)
Status [?] Resolved Driver
Version 0.134u2 Fixed in Version 0.147u1 Build Debug
Fixed in Git Commit Github Pull Request #
Summary 03464: All sets in seattle.c: MAME crash when try to read the voodoo region
Description When you try to read the voodoo region, mame crash.
Steps To Reproduce -run MAME with debug
-go on memory window
-go on address 880003a4

or

-run MAME with debug
-go on memory window
-change the address in physical (from options menu)
-go on address 80003a4
Additional Information I have also tried the last stable (0.134)
Github Commit
Flags
Regression Version
Affected Sets / Systems All sets in seattle.c
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
4
User avatar
No.05012
Tafoid
Administrator
Oct 6, 2009, 15:27
Backtrace (from u1) - using BLITZ

Program received signal SIGSEGV, Segmentation fault.
0x7800fa97 in setvbuf () from C:\WINNT\system32\msvcrt.dll
(gdb) bt
#0 0x7800fa97 in setvbuf () from C:\WINNT\system32\msvcrt.dll
#1 0x78021c79 in vsnprintf () from C:\WINNT\system32\msvcrt.dll
#2 0x00ab2ea4 in logerror (
    format=0x257d48c "VOODOO.%d.ERROR:Invalid attempt to read %s\n")
    at src/emu/mame.c:1225
Backtrace stopped: frame did not save the PC
(gdb) bt full
#0 0x7800fa97 in setvbuf () from C:\WINNT\system32\msvcrt.dll
No symbol table info available.
#1 0x78021c79 in vsnprintf () from C:\WINNT\system32\msvcrt.dll
No symbol table info available.
#2 0x00ab2ea4 in logerror (
    format=0x257d48c "VOODOO.%d.ERROR:Invalid attempt to read %s\n")
    at src/emu/mame.c:1225
        arg = 0x22f784 ""
        mame = (mame_private *) 0xb991f68
        cb = (callback_item *) 0x0
        machine = (running_machine *) 0xb981efc
User avatar
No.05013
etabeta
Developer
Oct 6, 2009, 16:54
edited on: Oct 6, 2009, 16:54
hence, it seems the read simply hits a debug fatal error left by Aaron in the code. not sure if it has been left on purpose though
User avatar
No.08937
Firewave
Senior Tester
Sep 21, 2012, 16:34
The error is actually in the logerror call:

logerror("VOODOO.%d.ERROR:Invalid attempt to read %s\n", v->index, v->regnames[regnum]);

v->regnames has a size of 225 and regnum is 233. I will commit a fix later on .
User avatar
No.08956
Firewave
Senior Tester
Sep 24, 2012, 13:58
Fixed in r18112