[Mono-bugs] [Bug 58656][Maj] Changed - Crash with corrupt stack, while running MonoDevelop

[bugzilla-daemon@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 tberman@gentoo.org.

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

--- shadow/58656	2004-05-20 08:26:11.000000000 -0400
+++ shadow/58656.tmp.7194	2004-05-21 22:10:15.000000000 -0400
@@ -87,6 +87,32 @@
 I get a similar crash with gnunit. It crashes when running the
 CodeAccessPermissionTest corlib test. It works ok if I run the test
 with nunit-console.
 
 ------- Additional Comments From lluis@ximian.com  2004-05-20 08:26 -------
 It works for me if I update from CVS with the tag D2004.05.13.22.00.00
+
+------- Additional Comments From tberman@gentoo.org  2004-05-21 22:10 -------
+This appears to be two seperate issues, one is fixed, one is not.
+
+first one was a JIT issues manifesting with all those warnings, and
+seems to be completely fixed. The second is far more subtle.
+
+The Mono.Runtime class was removed from corlib. This allowed access to
+the InstallSignalHandlers icall in the runtime, to fix the signal
+handlers up.
+
+any application using Gnome.Program needs this functionality, as gnome
+does funny stuff with signal handlers for the crash dialog and other
+things (maybe).
+
+So until this class is added back in, all gnome programs will
+basically immediatly segfault.
+
+You can disable this by exporting GNOME_DISABLE_CRASH_DIALOG=1 and
+then running the application.
+
+I will attempt to talk to miguel/gonzalo and figure out exactly why
+that class was removed, and how to expose its functionality elsewhere
+if that is what needs to happen.
+
+When it gets fixed, I will close this bug.