[Mono-bugs] [Bug 72539][Maj] Changed - SynchronizationAttributeTest.TestSynchronization hangs on 2.0 profile

[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=72539

--- shadow/72539	2005-07-04 16:30:58.000000000 -0400
+++ shadow/72539.tmp.27032	2005-07-04 17:11:11.000000000 -0400
@@ -4,13 +4,13 @@
 OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
 Priority: Major
-Component: misc
+Component: io-layer
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: bmaurer at users.sf.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
@@ -108,6 +108,11 @@
 
 ------- Additional Comments From bmaurer at users.sf.net  2005-07-04 16:30 -------
 From what I do trust of this stacktrace, it seems like this is coming
 from io-layer or the GC. The pthread functions seem to be called
 directly -- without using CriticalSection. The only places this can
 happen are in the gc and in io-layer.
+
+------- Additional Comments From bmaurer at users.sf.net  2005-07-04 17:11 -------
+The only seems to have 1 lock that ever gets used (when || marking
+isn't enabled), so thats not what is deadlocking. As an educated
+guess, am pinning the blame on the io-layer.