[Mono-bugs] [Bug 76841][Nor] New - 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 17:33:22 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 trow at ximian.com.


--- shadow/76841	2005-11-28 17:33:22.000000000 -0500
+++ shadow/76841.tmp.15039	2005-11-28 17:33:22.000000000 -0500
@@ -0,0 +1,49 @@
+Bug#: 76841
+Product: Mono: Runtime
+Version: 1.1
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: trow at ximian.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: some sort of race can crash the runtime at start-up
+I am using mono 1.1.10 on suse 10.0.
+In bludgeon (a testing tool for Beagle), I spawn off a beagled process and
+then immediately start sending 'ping' messages to it every 50ms.  We do
+this until the daemon responds, and then we know that it is ready to accept
+other messages.
+About one time out of three, the beagled's helper process runtime segfaults:
+Native stacktrace:
+        mono-beagled-helper(mono_handle_native_sigsegv+0xba) [0x81471da]
+        mono-beagled-helper [0x81354cf]
+        [0xffffe440]
+        mono-beagled-helper [0x80fc552]
+        mono-beagled-helper(mono_once+0xc6) [0x8102a66]
+        mono-beagled-helper [0x80fc68c]
+        mono-beagled-helper(mono_runtime_init+0xc9) [0x80daec9]
+        mono-beagled-helper [0x8136431]
+        mono-beagled-helper(mono_main+0x194) [0x805ce94]
+        mono-beagled-helper(__fxstat64+0x12b) [0x805bf3b]
+        /lib/tls/libc.so.6(__libc_start_main+0xd0) [0x40135ea0]
+        mono-beagled-helper(sinh+0x41) [0x805be91]
+This is very mysterious: I do not know why sending messages to the beagled
+would cause the helper process to crash.  We might be doing something
+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.

More information about the mono-bugs mailing list