| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 03657 | Crash/Freeze | Critical (emulation) | Random | Jan 10, 2010, 22:23 | May 13, 2010, 00:39 |
| Tester | Clark Kent | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Firewave | Resolution | Fixed | OS | Windows XP (32-bit) |
| Status [?] | Resolved | Driver | |||
| Version | 0.136 | Fixed in Version | 0.138 | Build | Normal |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 03657: All sets in maxaflex.c: Random crashes | ||||
| Description |
This driver is suffering from unknown and yet identified random crashes. All new discoveries should be added as notes to this report. |
||||
| Steps To Reproduce | |||||
| Additional Information |
mf_flip - crashes randomly, on my machine on level 8, on a friends computer on level 6. emulator quits suddenly. (Clark Kent) mf_bdash - Crashes randomly at level 3 and mame quits without any error message. (Scagazza) |
||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | All sets in maxaflex.c | ||||
|
Attached Files
|
 0000.png (5,143 bytes) May 11, 2010, 13:19 | ||||
 No.05484
Tafoid Administrator
Jan 11, 2010, 03:46
edited on: Jan 12, 2010, 17:45
|
I can acknowledge it happened once for me after several tries of level 8, but it was only in a regular build. I'll look at this more later. |
|---|---|
 No.05542
Clark Kent Tester
Jan 18, 2010, 21:53
|
I downloaded another version of mf_flip with another creation date but it still crashes in level 8. The emulators quits there without any error message. A friend of mine also tested it and it crashes there, too. No special treatment for the official MAME version - just play it till level 8 and it will crash. |
|
No.06074
Firewave Senior Tester
May 10, 2010, 15:46
|
I was able to pass level 8 in mf_flip with 0.137u4 without any crash. I also went up to level 10. |
|
No.06080
Scagazza Tester
May 11, 2010, 11:32
|
I tested mf_bdash with 0.137u4 and mame still quits randomly at level 3 without error messages |
|
No.06081
Haze Senior Tester
May 11, 2010, 13:20
|
I'm not seeing a crash, but the graphics seem to randomly go a bit nuts on the black tiles (seen it on level 2 and 3) I don't know this version of the game well, but it doesn't look intentional, almost like the memory is being trashed for a few frames now and again? Can anybody confirm if the game is meant to do this, or if this is just another indication that there is something wrong in the driver.. stack corruption or whatever else. |
|
No.06082
Firewave Senior Tester
May 11, 2010, 13:39
|
I was also able to finish level 3 of mf_bdash. Could you run it in gdb (gdb --args mame.exe mf_bdash) see, if you encounter something like a Segmentation Fault and post the backtrace (bt full) here? If it just exits try to set a breakpoint on the function exit() (IIRC) and post that backtrace. |
|
No.06090
Scagazza Tester
May 12, 2010, 09:45
|
Well I don't know if this could help: C:\MAME>gdb mame GNU gdb (GDB) 7.0.50.20091224-cvs Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-w64-mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from C:\MAME/mame.exe...done. (gdb) run mf_bdash -window Starting program: C:\MAME/mame.exe mf_bdash -window [New Thread 2128.0x89c] warning: Can not parse XML library list; XML support was disabled at compile tim e [New Thread 2128.0x304] [New Thread 2128.0x740] [New Thread 2128.0x368] [New Thread 2128.0xb0c] [New Thread 2128.0x31c] [New Thread 2128.0x8d8] [New Thread 2128.0xa68] [New Thread 2128.0xa3c] warning: assert: src/emu/sound/speaker.c:131: device != NULL Program received signal SIGTRAP, Trace/breakpoint trap. 0x0000000077ef2aa1 in ?? () (gdb) bt #0 0x0000000077ef2aa1 in ?? () #1 0x000000000195453e in osd_break_into_debugger ( message=0x10885308 "assert: src/emu/sound/speaker.c:131: device != NULL") at src/osd/windows/winmisc.c:168 #2 0x0000000001979b08 in emu_fatalerror (this=0x10885300, format=0x32e6578 "assert: %s:%d: %s") at src/emu/emucore.h:291 #3 0x0000000001878787 in get_safe_token (device=0x0) at src/emu/sound/speaker.c:131 #4 0x0000000001879528 in speaker_level_w (device=0x0, new_level=1) at src/emu/sound/speaker.c:267 #5 0x00000000005b6520 in mcu_portA_w (space=0xfc824f0, offset=0, data=249 '¨') at src/mame/drivers/maxaflex.c:56 #6 0x0000000000dc6080 in write_byte_generic (space=0xfc824f0, byteaddress=0, data=249 '¨') at src/emu/memory.c:590 #7 0x0000000000dd1f6b in memory_write_byte_8be (space=0xfc824f0, address=0, data=249 '¨') at src/emu/memory.c:4270 #8 0x0000000001288ec5 in bset (cpustate=0x278270, bit=128 '\200') at src/emu/cpu/m6805/6805ops.c:74 #9 0x00000000012917cf in cpu_execute_m6805 (device=0x278170, cycles=1) at src/emu/cpu/m6805/m6805.c:570 #10 0x0000000000dd535f in cpuexec_timeslice (machine=0x273920) at src/emu/cpuexec.c:328 #11 0x0000000000dbfe3c in mame_execute (options=0x3ea550) at src/emu/mame.c:320 #12 0x000000000103f86c in cli_execute (argc=3, argv=0x3e7880, osd_options=0x28c3920) at src/emu/clifront.c:177 #13 0x0000000000ce4f08 in utf8_main (argc=3, argv=0x3e7880) at src/osd/windows/winmain.c:318 #14 0x0000000001954406 in wmain (argc=3, argv=0x3e7310) at src/osd/windows/main.c:82 #15 0x000000000040141e in __tmainCRTStartup () at ../mingw-w64-crt/crt/crtexe.c:268 #16 0x0000000077d5964c in ?? () #17 0x0000000077d59620 in ?? () #18 0x0000000000000000 in ?? () (gdb) |
|
No.06091
Firewave Senior Tester
May 12, 2010, 10:08
edited on: May 12, 2010, 10:10
|
Definitely. The issue is obvious:speaker_level_w(0, data >> 7); The first parameter is running_device*, but it passes a NULL pointer. Replace the line with speaker_level_w(devtag_get_device(space->machine, "speaker"), data >> 7); and it should be working. |
|
No.06092
Firewave Senior Tester
May 12, 2010, 10:15
edited on: May 12, 2010, 10:41
|
I am just a bit baffled, that it's caused by an assert/fatalerror, but you say there was no message when MAME exited, since I can clearly see it when you ran gdb "warning: assert: src/emu/sound/speaker.c:131: device != NULL". |
|
No.06094
Scagazza Tester
May 12, 2010, 11:53
edited on: May 12, 2010, 11:55
|
Now there is another problem at level 3, this seems to be random too. You can hear a beep sound like when your time is ending but that's not true cos' the timer is not at zero, then you will not able to move the character of the game anymore. Also sometimes the level is incorrect displayed as 1.2 or 1.4 instead of 1.3. |
|
No.06096
Scagazza Tester
May 12, 2010, 12:44
|
Same random beep issue in mf_brist |
|
No.06097
Firewave Senior Tester
May 12, 2010, 13:00
|
Since the speaker call it should now produce a sound instead of an assert, so I am not surprised it's beeping now. Seems like there's an issue with the MCU code then, but that would be a different report. Same with the level display. Please open new reports for those issues. |