[Mono-bugs] [Bug 75034][Nor] Changed - Mono segmentation fault - instant killer death of mono

[bugzilla-daemon at 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 jonpryor at vt.edu.

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

--- shadow/75034	2005-05-24 18:08:00.000000000 -0400
+++ shadow/75034.tmp.18679	2005-05-24 18:20:55.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 75034
 Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: NOTABUG
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: alexmipego at hotmail.com               
 QAContact: mono-bugs at ximian.com
@@ -25,6 +25,20 @@
 testcase
 
 
 ------- Additional Comments From bmaurer at users.sf.net  2005-05-24 18:08 -------
 We can't really help that. You need to use the GLib functions to do
 timers so you get a callback on teh gui thread.
+
+------- Additional Comments From jonpryor at vt.edu  2005-05-24 18:20 -------
+There are two issues with the code:
+
+1.  It uses threads improperly with Gecko#.  This is what the GLib
+functions would fix.  This isn't what the bug report is about.
+
+2.  Mono dies because of (1).  *This* is the reported bug.  Mono
+normally converts SIGSEGV into a NullReferenceException.  Why wasn't
+that done here?  Why wasn't any effort made to cleanly shutdown the
+app -- run finalizers, look for exception handlers, print out a stack
+trace...?  Why did mono just die?
+
+In short, we expect better from mono in the presence of buggy apps. :-)