https://bugs.winehq.org/show_bug.cgi?id=55439
Eric Pouech eric.pouech@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED
--- Comment #14 from Eric Pouech eric.pouech@gmail.com --- thanks for your answers: - from #12 & #13, and looking at ruby's source, a conclusion could be that it's the game that closes itself if the write to output fails... (and not ruby) - as trick in #10 succeeds in #13, it's likely that the cause of the problem lies in "std handles not being cleared out on process inheritance on some options combinations"... the trick in #10 forces the std handles of the first process to be 0, and then inherited by children
A correct fix for this is on my todo list, but I'm afraid it'll take some time to make its way into Wine (if it's ever accepted and it has to touch some sensible areas).
As a temporary workaound, using the trick in #10 or setting WINEDEBUG are viable options