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

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

--- shadow/66614	2004-10-13 09:55:52.000000000 -0400
+++ shadow/66614.tmp.15025	2004-10-13 17:16:00.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 66614
 Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Major
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: james@ximian.com               
 QAContact: mono-bugs@ximian.com
@@ -180,6 +180,11 @@
 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.
+
+------- Additional Comments From dick@ximian.com  2004-10-13 17:16 -------
+The current theory is that this is being caused by a buffer overflow
+in libredcarpet.  I'm closing this as NOTABUG, reopen if it turns out
+to be a mono bug after all.