[Mono-bugs] [Bug 74154][Maj] Changed - Mutex class locks on OS X in simple application

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 13 Apr 2005 13:50:17 -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 cgaisford@novell.com.


--- shadow/74154	2005-04-13 10:43:36.000000000 -0400
+++ shadow/74154.tmp.29582	2005-04-13 13:50:17.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 74154
 Product: Mono: Runtime
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
 Severity: Unknown
 Priority: Major
 Component: io-layer
 AssignedTo: dick@ximian.com                            
 ReportedBy: cgaisford@novell.com               
 QAContact: mono-bugs@ximian.com
@@ -87,6 +87,28 @@
 ------- Additional Comments From dick@ximian.com  2005-04-13 10:43 -------
 The new io-layer is now merged, so I'm closing this bug as fixed.
+------- Additional Comments From cgaisford@novell.com  2005-04-13 13:50 -------
+I ran the test code on a dual G5 and it appear not to be fixed.  When
+the test code runs, a thread does a mux.WaitOne() (mux being a mutex).
+ When it obtains the mutex, the thread prints out 5 characters.  There
+are multiple threads that do this in multiple processes.  The output
+should be something like this:
+if you ever see a line like this:
+then the mutex is not preventing multiple threads or processes from
+obtaining it.
+Before the new io-layer was merged, this test would lock up.  Now it
+doesn't lock up, but I see mixed characters which indicates the mutex
+is not working.