[Mono-bugs] [Bug 75034][Nor] Changed - Gecko# segfault not converted to NullRef

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed May 25 06:33:20 EDT 2005


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 vargaz at gmail.com.

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

--- shadow/75034	2005-05-24 20:39:10.000000000 -0400
+++ shadow/75034.tmp.24443	2005-05-25 06:33:20.000000000 -0400
@@ -65,6 +65,15 @@
 
 Why shouldn't Gecko# be any different?
 
 ------- Additional Comments From bmaurer at users.sf.net  2005-05-24 20:39 -------
 Depends on the type of segfault. If it is stack overflow thats not our
 issue (well, its a dup of another bug...)
+
+------- Additional Comments From vargaz at gmail.com  2005-05-25 06:33 -------
+IMHO, mono should not convert a SIGSEGV in unmanaged code to a
+NullReferenceException *ever*. Net 2.0 throws an
+AccessViolationException in this case, but since a segmentation fault
+can also corrupt runtime data structures, the stack, the heap etc. we
+can't guarantee that an exception will be thrown. 
+
+


More information about the mono-bugs mailing list