[Mono-bugs] [Bug 74869][Maj] New - Signal handlers problem on os x.

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by joe@otee.dk.

http://bugzilla.ximian.com/show_bug.cgi?id=74869

--- shadow/74869	2005-05-08 11:42:42.000000000 -0400
+++ shadow/74869.tmp.28781	2005-05-08 11:42:42.000000000 -0400
@@ -0,0 +1,37 @@
+Bug#: 74869
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: joe@otee.dk               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Signal handlers problem on os x.
+
+When a null exception is thrown in mono on os x, it will invoke the crashreporter. 
+This is a known bug in os x, where the crashreporter is invoked although there is a null 
+exception signal handler. I filed a bug on this with Apple but they refuse to fix the issue.
+http://developer.apple.com/technotes/tn2004/tn2123.html (CrashReporter Limitations)
+
+
+The crashreporter will write the crashlog. In the case of a GUI application it will also popup the 
+crashreporter application.
+
+In a GUI application this makes people think the application crashed while it actually is still 
+running because mono catched the null exception.
+
+So for gui applications this is a real issue.
+
+One way to solve this is to use mach-o exception handlers instead of signals:
+http://www.omnigroup.com/mailman/archive/macosx-dev/2000-June/002030.html
+
+I asked Timothy J. Wood if this will make the crashreporter not popup. And he confirmed that it
+will not pop it up and not write a crashlog.