https://bugs.winehq.org/show_bug.cgi?id=51223
--- Comment #3 from C. Leu kle@bluewin.ch --- Hi Rémi Bernon
I am unfortunately in this programming context a total beginner. All that bisection stuff seems for me really really complex. ;-)
But I was able to provoke a new error message "Unhandled page fault" right after the "wineusb" one. Even more, the CXBX-R Xbox emulator crashes right after that. In the attachment you find a backtrace.
00c4:err:wineusb:event_thread_proc Error handling events: System call interrupted (perhaps due to signal) 00c4:err:wineusb:event_thread_proc Error handling events: System call interrupted (perhaps due to signal) wine: Unhandled page fault on read access to 00000000 at address 666C264A (thread 0110), starting debugger...
You are most likely able to reproduce this with any XInput controller. Here you find the latest build (take the VS2019 one): https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/releases/tag/CI-ba9ee5f
You just need the "winetricks -q d3dcompiler_47" argument, the built-in doesn't work. Nothing else is needed to replicate that error.