[Mono-bugs] [Bug 74525][Min] Changed - Thread.Interrupt problem on Gentoo

[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 miguel at ximian.com.

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

--- shadow/74525	2007-01-02 07:26:24.000000000 -0500
+++ shadow/74525.tmp.27125	2007-03-18 13:14:10.000000000 -0500
@@ -3,21 +3,21 @@
 Version: 1.1
 OS: other
 OS Details: Fedora Core 3
 Status: REOPENED   
 Resolution: 
 Severity: Unknown
-Priority: Normal
+Priority: Minor
 Component: misc
 AssignedTo: dick at ximian.com                            
 ReportedBy: christiano at croesus.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: jan.oravec at 6com.sk,jesse.sightler at gmail.com
-Summary: Thread.Interrupt not implemented
+Summary: Thread.Interrupt problem on Gentoo
 
 Description of Problem:
 Thread.Interrupt does not seem to work properly. Using Thread.Abort() is 
 not a viable solution here.
 
 
@@ -270,6 +270,43 @@
 T2 being asked to quit.
 T2 leaving. Bye!
 T1 leaving. Bye!
 
 It works fine on Mono/Linux if I run mono with --trace=all, and it 
 also works fine on Mono/Windows.
+
+------- Additional Comments From miguel at ximian.com  2007-03-18 13:14 -------
+This is what I get on Linux:
+Linux erandi 2.6.16.37-0.23-smp #1 SMP Mon Feb 19 14:25:39 UTC 2007
+i686 i686 i386 GNU/Linux
+
+This is with SUSE though.
+
+T1 getting lock...T2 getting lock...T1 getting lock...T2 getting lock...
+T1 got the lock.
+T1 sleeping for 10 ec...
+
+T1 woke up. Pulse and wait now...
+T2 got the lock.
+T2 sleeping for 5 sec...
+T2 woke up. Pulse and sleep 1 sec now...
+T2 releasedlock.T2 releasedlock.T1 woke up. Stopping T2 in 10 sec...
+
+T2 getting lock...
+T1 stopping T2 now.
+T2 got the lock.
+T2 sleeping for 5 sec...
+T2 being asked to quit.
+T2 leaving. Bye!
+T1 released lock and waiting for T2.
+T1 leaving. Bye!
+
+(The messages are a bit busted because I edited the copy-pasted output
+and killed a few chars accidentally).
+
+With Gentoo we have our share of problems with thread support, but I
+do not think anyone has collected a list of all the problems that
+people have with them, its never been on our radar.
+
+Am going to set this bug to Minimal priority and change the subject
+until we get more information.
+Miguel.