http://bugs.winehq.org/show_bug.cgi?id=56565 --- Comment #5 from Patrick Hibbs <hibbsncc1701@gmail.com> --- In a 64-bit clean wineprefix we get a div by zero on launch of setup.exe, ----snip---- wine: Unhandled division by zero at address 7EA1B7FE (thread 0024), starting debugger... ----snip---- doesn't matter if it's executed directly via command line or via double clicking setup.exe in wine explorer, or using the "Run As Administrator" context menu option in wine explorer. Making matters worse, the debugger is launched but although the winedbg process shows up in ps's output, we don't see it's dialog window anywhere. Nor does it appear on the WM's taskbar. So we can't switch to it or close it and it has to be killed manually. Trying to get back the terminal resulted in a X Error (BadWindow) message. In a 32-bit clean wineprefix on first launch winecfg loads, but the second we move the mouse cursor outside of the window, we get a div by zero error. On every subsequent launch of winecfg, we get a div by zero when launching winecfg and the window never appears. Making this issue worse, attempting to kill the non-visible 32-bit winedbg process results in yet more div by zero errors. Which results in more copies of winedbg launching. Making it very difficult to kill the running wine prefix, as a normal shutdown of wine is impossible at this point. (wineserver has to be killed to prevent spawning new winedbg processes, then each wine process has to be killed manually, with each winedbg process being sigterm'd && sigkill'd to get rid of it.) So this cannot be tested on wine-11.13. I will say that other 64-bit programs work under wine-11.13, even games that use DXVK or vkd3d-proton, so this may just be something wrong with 32-bit mode. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.