- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
05951 | Crash/Freeze | Critical (emulator) | Always | Jun 2, 2015, 19:05 | Jan 11, 2018, 12:19 |
Tester | NekoEd | View Status | Public | Platform | SDLMAME |
Assigned To | Resolution | Open | OS | Linux | |
Status [?] | Confirmed | Driver | nwk-tr.c | ||
Version | 0.162 | Fixed in Version | Build | Normal | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 05951: All in nwk-tr.c: Segmentation fault | ||||
Description | These games will segfault at a random time after booting. | ||||
Steps To Reproduce |
thrilld and clones: Start game and wait, or play a game. What you or the game is doing does not seem to matter. racingj and clones: Start game and wait for the point where graphics should appear. It will crash. |
||||
Additional Information |
One crash in thrilldb was not a segfault but a MAME exception, reporting the following: FATALERROR: sharc_iop_r: Unimplemented IOP reg 81 at 00022473 thrilldae cannot be tested as it does not boot. It should be noted however that this game does not seem to segfault. |
||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | All in nwk-tr.c | ||||
Attached Files
|
|||||
Relationships
Notes
4
![]() No.11706
B2K24 Moderator
Jun 2, 2015, 19:23
edited on: Jun 2, 2015, 19:25 |
On my official windows build, I launched thrilld and watched the attract mode run for about 5-8 minutes. After that time MAME closed itself with a stack crawl message.----------------------------------------------------- Exception at EIP=0000000001D556B9 (adsp21062_device::execute_run()+0x0169): ACCE SS VIOLATION While attempting to read memory at 0000000209F8EDAC ----------------------------------------------------- RAX=00000000FFFA0000 RBX=000000000A04A0C0 RCX=0000000000000000 RDX=0000000000000 000 RSI=0000000006D5517C RDI=0000000000000FA0 RBP=0000000000228A90 RSP=0000000000228 A70 R8=0000000000000448 R9=0000000000000000 R10=00000000187F3C10 R11=0000000001D4E 2B0 R12=0000000007F97D00 R13=0000000007F97D00 R14=0000000007F97D00 R15=000000000022F 588 ----------------------------------------------------- Stack crawl: 0000000000228A80: 0000000001D556B9 (adsp21062_device::execute_run()+0x0169) 0000000000228B40: 00000000024A06F1 (device_scheduler::timeslice()+0x04b1) 0000000000228BA0: 00000000024AD4F8 (running_machine::run(bool)+0x0188) 000000000022F690: 00000000024A1C4B (machine_manager::execute()+0x024b) 000000000022F840: 00000000025474EB (cli_frontend::execute(int, char**)+0x0d9b) 000000000022FDF0: 00000000014CDBE4 (utf8_main(int, char**)+0x0174) 000000000022FE50: 00000000028ECCFE (wmain+0x007e) 000000000022FF20: 00000000004013CA (__tmainCRTStartup+0x024a) 000000000022FF50: 00000000004014F8 (mainCRTStartup+0x0018) 000000000022FF80: 00000000768559DD (BaseThreadInitThunk+0x000d) 000000000022FFD0: 0000000076F4A651 (RtlUserThreadStart+0x0021) |
---|---|
![]() No.11707
NekoEd Senior Tester
Jun 2, 2015, 19:29
edited on: Jun 2, 2015, 19:30 |
"ACCESS VIOLATION" is what Windows calls a "Segmentation Fault". Just a different name for the same mechanism. |
![]() No.14646
Firewave Senior Tester
Jan 10, 2018, 22:07
|
Some testing with 0.193 racingj, racingj2, racing2j Was reported as MT05632 and is fixed in 0.194 Fatal error: SHARC: Loop Stack underflow! thrilldae Does not boot - fails with "RTC SELF CHECK ERROR" . Since this is marked MACHINE_NOT_WORKING it is not a valid report. thrilld, thrilldb thrilld crashed on Linux. On Windows with the official binary both froze for me once. This is the only valid and remaining issue here ==235949==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x00000d888432 bp 0x7ffcbd1f4f30 sp 0x7ffcbd1f4c20 T0) |
![]() No.14648
Osso Developer
Jan 11, 2018, 09:50
edited on: Jan 11, 2018, 10:00 |
Also MAME crashes when putting the "test mode" dip-switch on, resetting and letting the game run through the rom tests. It only seems to happen with -video d3d. Apparently with 0.144 it worked, with 0.145 it exited without crash, from 0.146 onwards it crashes. |