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

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 13 Oct 2004 09:55:52 -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 lupus@ximian.com.


--- shadow/66614	2004-09-28 11:18:32.000000000 -0400
+++ shadow/66614.tmp.4237	2004-10-13 09:55:52.000000000 -0400
@@ -171,6 +171,15 @@
 #12 0x080486f8 in main (argc=4, argv=0xbfffeef4) at main.c:6
 ------- Additional Comments From james@ximian.com  2004-09-25 10:23 -------
 The above trace seems to be a red herring.  I found the standard
 "finalizer hang" trace on a different thread.
+------- Additional Comments From lupus@ximian.com  2004-10-13 09:55 -------
+James: please report the stack traces from all the threads with the
+gdb command: t a a bt
+You may also want to check running your test case with the
+ASSUME_KERNEL env var set to something like 2.4.0 to force the use of
+the old threads package and see if this is related to the issue
+between libgc and nptl reported by others or if it is a deadlock
+inside mono itself.