-
Notifications
You must be signed in to change notification settings - Fork 2k
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on ssystem3 / saitek_ssystem3.cpp #5584
Comments
Looks like you don't have mame.sym, so unfortunately there's no useful info in that stack trace. The game works fine for me, both on my own MAME build and also on a daily build provided by Tafoid. When the official MAME binary is released, please try again on that version. |
Hi Hap, I built a debug / symbols version and here's the backtrace: (gdb) run ssystem3 -window Thread 1 received signal SIGSEGV, Segmentation fault. |
Interesting. mame ssystem3 -norc works. Something in the *.ini. Attached. |
Appears to not care for the ssystem3.zip artwork. When I remove that from my artwork folder it defaults to the internal layout and plays. With it it faults. c:\O\Games\MAME>mame ssystem3 -v Exception at EIP=0000000006478c5a (not found): ACCESS VIOLATION
|
The old external artwork no longer works, for all chess games. You need to remove it from your artpath. |
Does the old artwork pass |
Doesn't appear so; if I'm doing this right: |
Yeah, that looks like there's an error in the layout file itself that was somehow being ignored before. If you can't work it out, paste the content of the file here. |
The zip is in the comment above. I'll ping Mr. Do and let him know there may be trouble w/ the old chess layouts. Thanks - |
Right, that default.lay is broken. But then I don't understand why it didn't crash before my driver update.
Should have a closing tag, so at the least like this: |
I'm aware MAME should do better than crash on invalid layouts, but that's a known issue - invalid element nesting can cause MAME to crash. |
FWIW, as of fde41f3 MAME will print a warning and continue, ignoring the layout file. Now we can get bug reports from people saying artwork doesn't show when their layout files are actually malformed. |
0.212 (mame0212-684-g17e43dada2) / 9/2/2019 6am PST
Win10 x64
Attempts to run ssystem3 receive an immediate fault.
c:\O\Games\MAME>mame ssystem3
Exception at EIP=0000000005c10026 (not found): ACCESS VIOLATION
While attempting to read memory at 0000000000000010
RAX=000000000ded5500 RBX=0000000000000000 RCX=0000000000000000 RDX=000000000d55de4e
RSI=0000000011ccd990 RDI=000000000f9a9710 RBP=0000000011cf6b40 RSP=000000000f9a7920
R8=000000000a24d1b0 R9=0000000000000006 R10=0000000000000000 R11=8101010101010100
R12=000000000f9a7bd0 R13=0000000011ccd9c8 R14=000000000d54bb1f R15=0000000000000000
Stack crawl:
000000000f9a7950: 0000000005c10026 (not found)
000000000f9a7dd0: 00000000058614f9 (not found)
000000000f9a7fe0: 00000000058491c3 (not found)
000000000f9a8d60: 000000000584a8f7 (not found)
000000000f9a8db0: 000000000584d889 (not found)
000000000f9a8e20: 000000000584da46 (not found)
000000000f9a8ee0: 0000000003bce99c (not found)
000000000f9a8f50: 0000000003bc9fe6 (not found)
000000000f9a9070: 0000000003bbfdb7 (not found)
000000000f9a9330: 0000000003bb858a (not found)
000000000f9a9420: 000000000583469b (not found)
000000000f9a94f0: 000000000583686a (not found)
000000000f9af1d0: 0000000003c74fc8 (not found)
000000000f9af440: 0000000003ce7f57 (not found)
000000000f9af610: 0000000003ce82bd (not found)
000000000f9af670: 0000000003c73067 (not found)
000000000f9afe20: 0000000009c084b7 (not found)
000000000f9afef0: 00000000004013a5 (not found)
000000000f9aff20: 000000000040150b (not found)
000000000f9aff50: 00007ffc885b7bd4 (BaseThreadInitThunk+0x0014)
000000000f9affd0: 00007ffc8a48cee1 (RtlUserThreadStart+0x0021)
The text was updated successfully, but these errors were encountered: