[Mono-bugs] [Bug 66614][Maj] Changed - apparent deadlock in runtime
Thu, 23 Sep 2004 17:55:46 -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 firstname.lastname@example.org.
--- shadow/66614 2004-09-23 13:21:08.000000000 -0400
+++ shadow/66614.tmp.22304 2004-09-23 17:55:46.000000000 -0400
@@ -10,12 +10,13 @@
Summary: apparent deadlock in runtime
I'm hitting what appears to be a deadlock in the runtime. All my threads
appear to be haulted, and the application does not repsond to ctrl-c (or
anything else). I attached with gdb, and got the following stack trace.
@@ -80,6 +81,31 @@
------- Additional Comments From email@example.com 2004-09-23 13:18 -------
Oh, /lib/tls/libc.so.6 has NPTL. So I do have it :)
------- Additional Comments From firstname.lastname@example.org 2004-09-23 13:21 -------
Also, using GC_DONT_GC=1 seems to "fix" the deadlock problem.
+------- Additional Comments From email@example.com 2004-09-23 17:55 -------
+This is a known (if ignored) bug. First mentioned here
+originally reported on Gentoo
+(http://bugs.gentoo.org/show_bug.cgi?id=54603), reported on this
+bugzilla here (http://bugzilla.ximian.com/show_bug.cgi?id=60576),
+incorrectly identified here
+(http://bugs.gentoo.org/show_bug.cgi?id=63734), clarified (and
+ignored) some what here
+finally to end up re reported here.
+Here is some possible evidence of this NOT being an NPTL bug, but a
+mono/libgc bug that is easier to reproduce when using NPTL
+This thread also makes for interesting reading
+as does this one
+I've done a lot of leg work with this bug, but I need some help here.
+When are the mono guys going to look into this, instead of just saying
+"it's a bug in nptl".