https://bugs.winehq.org/show_bug.cgi?id=57547
--- Comment #9 from T E Dixon dixonte+winehq@stc-networks.com --- Created attachment 77650 --> https://bugs.winehq.org/attachment.cgi?id=77650 1st attempt to use winedbg
(In reply to Bernhard Übelacker from comment #8)
Maybe you can recompile with such flags to configure: CFLAGS="-Og" CROSSCFLAGS="-Og" or CFLAGS="-g" CROSSCFLAGS="-g"
https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#compiler- optimizations--call-stacks
Because this issue is triggered by some interactive action, you might be able to attach a winedbg to the later failing winedevice.exe. Unfortunately there are three of it, in my environment that one with hidclass.sys loaded is in the "middle".
https://gitlab.winehq.org/wine/wine/-/wikis/Commands/winedbg
Okay, so I rebuilt with this: CFLAGS="-Og -fno-omit-frame-pointer" CROSSCFLAGS="-Og -fno-omit-frame-pointer"
I then tried reproducing the issue without the debugger. This time when the error dialogue pops up and I click Show Details, I get an empty dialogue box which instantly disappears.
I then tried using winedbg. This is new to me so I'm not sure if I'm doing it right. On my system there were either 1 or 2 winedevice.exe processes. I have tried attaching to both, and the debugger will stop the error dialogue from popping up if attached to the first one, so I assume that is the correct one.
This attachment is a log of the output from winedbg. I made sure to use the same WINEPREFIX for it as the 'wine control' command. Looks like I need to do something else to get the debug symbols?