 No.12681
Tourniquet Developer
May 20, 2016, 20:18
|
Suspicion was this was related to Brad's commit pre-vacation. |
|---|---|
|
No.12682
Tourniquet Developer
May 21, 2016, 01:01
|
This relates to XAudio. Doesn't crash with -sound dsound as suggested by Tafoid. |
 No.12683
B2K24 Senior Tester
May 21, 2016, 04:05
|
unable to reproduce here on my Win10 64-bit rig. *mame64 tnzs -sound xaudio2 -debug* doesn't crash on my end. Tried 10 or so different random games that use different drivers and am unable to reproduce any crash. |
|
No.12701
Tourniquet Developer
May 21, 2016, 21:48
|
As per message to the list: "Okay, VS2015 was very helpful. As per the MinGW/gdb stacktrace, it's a crash in window.cpp handling what it believes is a WM_USER_EXEC_FUNC message (WMUSER+7). It actually has a message->wParam of 0xBABE, which seems like a common/sentinel value. I only get these messages when XAudio is enabled, and this code is only reached when -debug is used in conjunction, presumably because the emulation starts paused. If I comment out the single line that executes wParam as a function pointer, then emulation and the debugger appears to function perfectly. So the question is - where are these events coming from? I note that the event polling is pass a nullptr to WaitMessage(), which seems to imply that we get all messages for the windows for the thread or other messages with no value set... I guess there's some crossover from the XAudio events, and that the imgui debugger, not having a Window, is fine." |
|
No.12704
Tourniquet Developer
May 22, 2016, 10:12
|
Committed fix for this for 0.174. Thanks to smf for clarifying. |