[Mono-bugs] [Bug 76841][Nor] Changed - some sort of race can crash the runtime at start-up

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Nov 28 20:04:50 EST 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 dick at ximian.com.

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

--- shadow/76841	2005-11-28 17:33:22.000000000 -0500
+++ shadow/76841.tmp.22816	2005-11-28 20:04:50.000000000 -0500
@@ -1,17 +1,17 @@
 Bug#: 76841
 Product: Mono: Runtime
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: misc
-AssignedTo: mono-bugs at ximian.com                            
+AssignedTo: dick at ximian.com                            
 ReportedBy: trow at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Summary: some sort of race can crash the runtime at start-up
 
@@ -44,6 +44,17 @@
 stupid in Beagle (so this might be our bug), but regardless --- we still
 shouldn't be able to crash the runtime.
 
 Sleeping for 1s before we start pinging allows us to avoid the crash, so
 this must be some sort of race in start-up.  Beagle's message-passing code
 uses async I/O, so the bug might be related to that.
+
+------- Additional Comments From dick at ximian.com  2005-11-28 20:04 -------
+Does bug 76731 (reported by Joe a couple of weeks ago) look like the
+same thing to you?
+
+If so, now that you've described a way to reproduce it I'll be able to
+take a look.  Could you look up the symbols between mono_once and the
+mono_handle_native_sigsegv please?
+
+The comment in the other bug about mono_once not having changed in
+years still stands, though.


More information about the mono-bugs mailing list