http://bugs.winehq.org/show_bug.cgi?id=14789 --- Comment #11 from Markus Elfring <Markus.Elfring(a)web.de> 2008-08-20 12:39:57 --- I would like to point out that the implementation for the function "segvhandler" is also not async-signal-safe. I'd prefer more respect for software correctness in this detail. http://source.winehq.org/git/wine.git?a=blob;f=tools/wmc/wmc.c;h=910a654b3c8... http://source.winehq.org/git/wine.git/?a=blob;f=tools/wrc/wrc.c;h=15f30a3e7d... I know that it means a couple of more work to get the affected parts completely right. Which behaviour do you expect on standard-compliant platforms if unsafe function calls are used? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.