https://bugs.winehq.org/show_bug.cgi?id=55439
Eric Pouech eric.pouech@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech@gmail.com
--- Comment #10 from Eric Pouech eric.pouech@gmail.com --- a wild guess is probably that after dcf0bf1f383f8429136cb761f5170a04503a297b, the process inheritance mechanism in Wine doesn't clear the inherited handles, which get "random" values... using WINEDEBUG forces the inheritance of the unix fd, which then can succeed when written to
I don't see any Wine related crash in the logs (after installing gnutls), perhaps it's the game that stops when write to output fails? Can you explicit what you mean by "game crashes in specific places"? do you mean it prints & stops, or does it mean it only prints?
To check if the wild guess is correct, can you the game with ./wine game < /dev/null >& /dev/null (you shouldn't get any output, but it could suppress the stops in the execution of the program if they existed)