[Mono-bugs] [Bug 75007][Maj] Changed - Deadlock with --debug

[bugzilla-daemon at 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 bmaurer at users.sf.net.

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

--- shadow/75007	2005-07-06 14:59:37.000000000 -0400
+++ shadow/75007.tmp.30499	2005-07-06 21:24:53.000000000 -0400
@@ -1,23 +1,23 @@
 Bug#: 75007
 Product: Mono: Runtime
 Version: 1.1
 OS: unknown
 OS Details: On mono 1.1.8.2, SMP
-Status: REOPENED   
+Status: NEW   
 Resolution: 
 Severity: Unknown
-Priority: Blocker
-Component: misc
-AssignedTo: mono-bugs at ximian.com                            
+Priority: Major
+Component: debug
+AssignedTo: martin at ximian.com                            
 ReportedBy: joeshaw at novell.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: matt.hargett at logiclibrary.com,trow at ximian.com
-Summary: Deadlock between loader and domain lock
+Summary: Deadlock with --debug
 
 Sorry, I'm not sure if this is a JIT bug or an IO layer bug.
 
 With the new messaging system we're using in Beagle, we are frequently
 getting hangs in a constructor for a class which handles socket connections
 on a Unix domain socket.  The constructor itself is very simple, it just
@@ -224,6 +224,9 @@
 Created an attachment (id=15443)
 stack trace
 
 
 ------- Additional Comments From joeshaw at novell.com  2005-07-06 14:59 -------
 oh, yeah, this is on 1.1.8.2 on an SMP box on SUSE 9.3.
+
+------- Additional Comments From bmaurer at users.sf.net  2005-07-06 21:24 -------
+This only happens with --debug