http://bugs.winehq.org/show_bug.cgi?id=14789
--- Comment #25 from Markus Elfring Markus.Elfring@web.de 2009-11-27 05:30:06 --- (In reply to comment #24)
Markus, I'm all for safe code, but pick your battles!
It would be easy to use the data type "sig_atomic_t" and to delete the misplaced fprintf() calls ...
As Alexandre said, this code only fires when the server is crashing, which should never happen.
The source code has got more open issues like "Check return codes everywhere" that result in different opinions about the involved probabilities. http://bugs.winehq.org/show_bug.cgi?id=14788
Could you spend some of your energy helping me triage buffer overruns (see http://kegel.com/wine/valgrind/logs/ )?
I assume that some of them can be cleaned up by more object-oriented programming (in C++).