https://bugs.winehq.org/show_bug.cgi?id=57547
--- Comment #16 from T E Dixon dixonte+winehq@stc-networks.com --- (In reply to Bernhard Übelacker from comment #15)
Does this crash in winedevice happen just with wine-staging, or are your own builds regular wine?
My own builds are regular wine.
With "--enable-win64" you were building just the 64-bit side. The build ommitting this was therefore just a 32-bit one. The "Building Wine" describes how to configure to tie both together.
That makes sense. So it seems the error only occurs in 64-bit builds, or with a 64-bit prefix at least.
You seem to have a few input devices connected - maybe you could disconnect some, so there is less output, and if just the mouse (and keyboard) is involved chances get better someone can replicate the crash.
I'll try that later today.
(In reply to T E Dixon from comment #14)
With this build I'm able to run wine64 and winedbg from the build directory. However the windbg output is still the same unhelpful page fault on write access in 64-bit code. I'm unsure how to proceed from here.
Does the output below "Backtrace:" still show only "hidclass.sys", or has it changed to a function name and maybe a line number?
If CFLAGS=-0g, regardless of if it was built by portage or by myself, the output is basically only what you can see in https://bugs.winehq.org/attachment.cgi?id=77650