[Mono-bugs] [Bug 74742][Wis] Changed - Runtime ability to disable internal signal handlers

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 26 Apr 2005 17:30:43 -0400 (EDT)


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@gmail.com.

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

--- shadow/74742	2005-04-26 15:07:14.000000000 -0400
+++ shadow/74742.tmp.14220	2005-04-26 17:30:43.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 74742
 Product: Mono: Runtime
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Wishlist
 Component: JIT
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: joeshaw@novell.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -24,6 +24,13 @@
 worthless because there isn't any stack information from the unmanaged code.
 
 When dealing with bugs like this, an environment variable, like
 MONO_DISABLE_SIGNAL_HANDLERS would be nice so that the runtime would just
 segfault (or whatever).  That way we can use gdb and other tools to attach
 to the process and get a more accurate stack trace to see what's going on.
+
+------- Additional Comments From vargaz@gmail.com  2005-04-26 17:30 -------
+A better solution would be to avoid converting segmentation faults in
+unmanaged code into NullReferenceExceptions, and abort the process 
+instead.
+
+