http://bugs.winehq.org/show_bug.cgi?id=14789 --- Comment #12 from Alexandre Julliard <julliard(a)winehq.org> 2008-08-21 07:38:40 --- There is no reason at all to worry about that fprintf, first because segv is actually not an async signal, second because the code aborts right away so we never even return from the handler, third because if the app is really crashing inside fprintf not seeing the final error is the least of your worries. There are more important issues to worry about than the theoretical standard compliance of a signal handler that never gets triggered anyway. -- 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.