[Mono-bugs] [Bug 74525][Nor] Changed - Thread.Interrupt not implemented
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Tue Jan 2 07:26:24 EST 2007
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 gert.driesen at pandora.be.
http://bugzilla.ximian.com/show_bug.cgi?id=74525
--- shadow/74525 2007-01-01 16:49:26.000000000 -0500
+++ shadow/74525.tmp.3215 2007-01-02 07:26:24.000000000 -0500
@@ -1,12 +1,12 @@
Bug#: 74525
Product: Mono: Runtime
Version: 1.1
OS: other
OS Details: Fedora Core 3
-Status: NEEDINFO
+Status: REOPENED
Resolution:
Severity: Unknown
Priority: Normal
Component: misc
AssignedTo: dick at ximian.com
ReportedBy: christiano at croesus.com
@@ -242,6 +242,34 @@
------- Additional Comments From miguel at ximian.com 2007-01-01 16:49 -------
Works for me; It takes a while though.
Please provide further stack traces, or the output of SIGQUIT when
this hangs.
+
+------- Additional Comments From gert.driesen at pandora.be 2007-01-02 07:26 -------
+Miguel, it never hangs on my Linux system but instead continues
+running forever since the T1 thread never manages to obtain the lock
+after T2 releases it.
+
+See the output I provided earlier (on 2006-11-06), and compare that
+to the output I get on MS:
+
+T1 getting lock...
+T1 got the lock.
+T1 sleeping for 10 sec...
+T2 getting lock...
+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 released lock.
+T2 getting lock...
+T1 woke up. Stopping T2 in 10 sec...
+T1 stopping T2 now.
+T1 released lock and waiting for T2.
+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.
More information about the mono-bugs
mailing list