- --
Viewing Issue Advanced Details
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 02141 | Crash/Freeze | Critical (emulator) | Have not tried | Aug 21, 2008, 06:20 | Jan 2, 2009, 04:15 |
| Tester | hotcoke | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | aaron | Resolution | Fixed | OS | Windows XP/Vista 32-bit |
| Status [?] | Resolved | Driver | |||
| Version | 0.127 | Fixed in Version | 0.129 | Build | Normal |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 02141: sunaq: At the Title, Game is Crash | ||||
| Description | At the Title, Game is Crash | ||||
| Steps To Reproduce | |||||
| Additional Information | it's windows specific: it doesn't happen on SDLMAME | ||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | sunaq | ||||
|
Attached Files
|
|||||
Relationships
| There are no relationship linked to this issue. |
Notes
9
|
No.02147
etabeta Developer
Aug 21, 2008, 06:54
|
I cannot reproduce this. I reach the title screen and then I can either let the attract sequence go as long as I want or start a game without any crash. |
|---|---|
|
No.02148
john_iv Senior Tester
Aug 21, 2008, 07:04
|
Repro in MameUI64. Launched game and then hit insert to unthrottle for 10 seconds or so.. then it access violated out. |
|
No.02150
etabeta Developer
Aug 21, 2008, 07:50
|
maybe it's then windows specific because I tried both debug and plain SDLMAME builds and I can run through 4 attract sequences without any problem |
|
No.02151
Tafoid Administrator
Aug 21, 2008, 08:25
|
I can crash it two ways on Windows 32-bit build from MAMEDEV: 1. Run game for 64 seconds (-str 64) and don't touch anything and a crash occurs. A game with -str 63 does not crash. 2. Begin emulation and anytime after the demonstration starts (Dog w/two boys) and I hit '5' to credit up, I get a crash. |
|
No.02154
Robbbert Moderator
Aug 21, 2008, 08:48
edited on: Aug 21, 2008, 08:49 |
I get EXACTLY the same as Tafoid. 32-bit build, self compiled, on XP 32-bit OS. The two crashes produce different information though. |
|
No.02156
etabeta Developer
Aug 21, 2008, 09:06
|
and both situations don't produce any crash on my mac with SDLMAME |
|
No.02157
robiza Developer
Aug 21, 2008, 10:31
|
add a snap: if instruction in 7c3e is executed the game crash register's values A0 and A1 are correct probably the problem is in the core |
|
No.03461
Firewave Senior Tester
Jan 2, 2009, 02:45
|
Backtrace of the -str 64 crash:
Program received signal SIGSEGV, Segmentation fault.
0x009b469b in read_byte_generic (space=0x12ee1750, byteaddress=4208)
at src/emu/memory.c:459
459 result = (*handler->bankbaseptr)[byteoffset];
(gdb) bt full
#0 0x009b469b in read_byte_generic (space=0x12ee1750, byteaddress=4208)
at src/emu/memory.c:459
handler = (const handler_data *) 0x12f11030
byteoffset = 112
entry = 1
result = 0 '
Backtrace of the "press 5 during title" case:
Program received signal SIGSEGV, Segmentation fault.
0x009b469b in read_byte_generic (space=0x13001750, byteaddress=61584)
at src/emu/memory.c:459
459 result = (*handler->bankbaseptr)[byteoffset];
(gdb) bt full
#0 0x009b469b in read_byte_generic (space=0x13001750, byteaddress=61584)
at src/emu/memory.c:459
handler = (const handler_data *) 0x13031030
byteoffset = 57488
entry = 1
result = 0 '
They appear to be the same issue with just different values. |
|
No.03469
aaron Developer
Jan 2, 2009, 04:15
|
SDLMAME seems to be more forgiving of invalid reads. The debug Windows build crashes reliably here, thanks to the guard pages. |