[Mono-bugs] [Bug 75034][Wis] Changed - gtk# segfault not converted to NullRef

[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 bmaurer at users.sf.net.

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

--- shadow/75034	2005-05-24 18:20:55.000000000 -0400
+++ shadow/75034.tmp.18811	2005-05-24 18:35:01.000000000 -0400
@@ -3,21 +3,21 @@
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: REOPENED   
 Resolution: 
 Severity: Unknown
-Priority: Normal
+Priority: Wishlist
 Component: misc
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: alexmipego at hotmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Mono segmentation fault - instant killer death of mono
+Summary: gtk# segfault not converted to NullRef
 
 Using the testcase I attach Mono (after 5 seconds) dies with segmentation
 fault. The gui isn't thread-safe, so thats a buggy code, yet Mono should
 handle this and throw an Exception, not a segmentation fault.
 
 ------- Additional Comments From alexmipego at hotmail.com  2005-05-24 08:57 -------
@@ -39,6 +39,12 @@
 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. :-)
+
+------- Additional Comments From bmaurer at users.sf.net  2005-05-24 18:35 -------
+Can we prove that the segfault was really a nullref?
+
+Btw, trying to catch this exception would be horrible. God only knows
+hot the gui libs have been corrupted.