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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=74525 --- shadow/74525 2006-11-06 08:34:59.000000000 -0500 +++ shadow/74525.tmp.22239 2006-11-06 12:07:51.000000000 -0500 @@ -190,6 +190,42 @@ The code provided by Christiano never stops running on Mono (it does on MS), but I think it's not related to the interrupt. ------- Additional Comments From [EMAIL PROTECTED] 2006-11-06 08:34 ------- The test case provided works fine for me. Can you give some more details? + +------- Additional Comments From [EMAIL PROTECTED] 2006-11-06 12:07 ------- +This is the output I get on my system (built from svn): + +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... +T2 got the lock. +T2 sleeping for 5 sec... +T2 woke up. Pulse and sleep 1 sec now... +T2 released lock. +T2 getting lock... +T2 got the lock. +T2 sleeping for 5 sec... +T2 woke up. Pulse and sleep 1 sec now... +T2 released lock. +T2 getting lock... +T2 got the lock. +T2 sleeping for 5 sec... +T2 woke up. Pulse and sleep 1 sec now... +T2 released lock. +T2 getting lock... +T2 got the lock. +T2 sleeping for 5 sec... +T2 woke up. Pulse and sleep 1 sec now... +T2 released lock. +... + +Apparently the T1 thread never (re)acquires the lock. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
