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

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 26 Apr 2005 15:07:14 -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 joeshaw@novell.com.


--- shadow/74742	2005-04-26 15:07:14.000000000 -0400
+++ shadow/74742.tmp.13235	2005-04-26 15:07:14.000000000 -0400
@@ -0,0 +1,29 @@
+Bug#: 74742
+Product: Mono: Runtime
+Version: 1.1
+OS Details: 
+Status: NEW   
+Priority: Wishlist
+Component: JIT
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: joeshaw@novell.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Runtime ability to disable internal signal handlers
+When you're using pinvoke a lot, there are often bugs in either the
+unmanaged code or the managed wrapper that can be hard to track down
+because the runtime overrides a lot of signals, like SIGSEGV, SIGILL,
+SIGBUS, and SIGFPE.  This is especially problematic with gtk#, because if
+there is a bug in code that gets executed from the main loop (like an idle
+function, timeout, etc.) the stack trace you get in managed code is pretty
+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.