[Mono-bugs] [Bug 66614][Maj] Changed - apparent deadlock in runtime

[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 james@ximian.com.

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

--- shadow/66614	2004-09-24 08:05:34.000000000 -0400
+++ shadow/66614.tmp.8353	2004-09-24 21:11:01.000000000 -0400
@@ -115,6 +115,26 @@
 by the strange options used to build gentoo packages."
 
 Now the same bug (or something looking like the same bug) has been
 seen in a distro with reproducible packages, we can do some serious
 debugging.
 
+
+------- Additional Comments From james@ximian.com  2004-09-24 21:11 -------
+#0  0xffffe410 in ?? ()
+#1  0xbfffe1e4 in ?? ()
+#2  0x00000002 in ?? ()
+#3  0x00000000 in ?? ()
+#4  0x40252c5e in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
+#5  0x4024fc1c in _L_mutex_lock_88 () from /lib/tls/libpthread.so.0
+#6  0x46900010 in ?? ()
+#7  0x0000000c in ?? ()
+#8  0x40197abc in __JCR_LIST__ () from /usr/local/lib/libmono.so.0
+#9  0x06000230 in ?? ()
+#10 0x06000230 in ?? ()
+#11 0xbfffe204 in ?? ()
+#12 0x4010872f in EnterCriticalSection (section=0x40199564)
+    at critical-sections.c:151
+Previous frame identical to this frame (corrupt stack?)
+
+
+I got this just now when it was locked up.