[Mono-bugs] [Bug 60412][Wis] Changed - bug with thread and mutex

[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 hannibalbundie@hotmail.com.

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

--- shadow/60412	2004-06-18 08:09:34.000000000 -0400
+++ shadow/60412.tmp.19829	2004-06-18 11:36:23.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 60412
 Product: Mono: Runtime
 Version: unspecified
-OS: unknown
-OS Details: Red Hat 9.0 / kernel 2.4.22 with AC1 patch and nptl patch
-Status: NEEDINFO   
+OS: Red Hat 9.0
+OS Details: kernel 2.4.22 with AC1 patch and nptl patch
+Status: REOPENED   
 Resolution: 
 Severity: Unknown
 Priority: Wishlist
 Component: packaging
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: hannibalbundie@hotmail.com               
@@ -58,6 +58,62 @@
 With current CVS I get an unending output of
 
                 ---> AddTrace : mutex.WaitOne() ... ok
 
 so this seems to be working.  Please add more info if you can pin the
 bug down.
+
+------- Additional Comments From hannibalbundie@hotmail.com  2004-06-18 11:36 -------
+Thanks for your interest,
+
+
+the unending output of
+
+                ---> AddTrace : mutex.WaitOne() ... ok
+
+is the result that I always have with mint and sometimes with mono.
+But as I have said before, it's not the expected result.
+
+
+Today, with mono I very often have the following output :
+
+                ---> AddTrace : mutex.WaitOne() ... ok
+                ---> AddTrace : mutex.WaitOne() ... ok
+Run TaskManager ... TaskManager is running
+                ---> AddTrace : mutex.WaitOne() ... ok
+                ---> AddTrace : mutex.WaitOne() ... ok
+                ---> AddTrace : mutex.WaitOne() ... ok
+ 
+====> ThreadProc 1
+                ---> AddTrace : mutex.WaitOne() ...
+
+So, we can see that mutex.WaitOne() freezes at the first call of
+ThreadProc.
+
+
+In a perfect world, the unending output would be :
+
+                ---> AddTrace : mutex.WaitOne() ... ok
+                ---> AddTrace : mutex.WaitOne() ... ok
+Run TaskManager ... TaskManager is running
+                ---> AddTrace : mutex.WaitOne() ... ok
+                ---> AddTrace : mutex.WaitOne() ... ok
+                ---> AddTrace : mutex.WaitOne() ... ok
+ 
+====> ThreadProc 1
+                ---> AddTrace : mutex.WaitOne() ... ok
+====> OK
+                ---> AddTrace : mutex.WaitOne() ... ok
+
+====> ThreadProc 2
+                ---> AddTrace : mutex.WaitOne() ... ok
+====> OK
+                ---> AddTrace : mutex.WaitOne() ... ok
+
+====> ThreadProc 3
+                ---> AddTrace : mutex.WaitOne() ... ok
+====> OK
+                ---> AddTrace : mutex.WaitOne() ... ok
+
+etc ... etc ...
+If you run the test program on Windows you will see the above output.
+(But I haven't said that Windows is the perfect world :-) )