[Mono-bugs] [Bug 77208][Nor] Changed - in MS.Net 2.0, finally blocks are not interrupted by ThreadAbortExceptions/Interrupt

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu May 17 19:59:07 EDT 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 macite at gmail.com.

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

--- shadow/77208	2007-05-17 09:51:42.000000000 -0400
+++ shadow/77208.tmp.2666	2007-05-17 19:59:07.000000000 -0400
@@ -92,6 +92,15 @@
 Repro #2: use NET_2_0 symbol when compiling for 2.0 profile
 
 
 ------- Additional Comments From gert.driesen at pandora.be  2007-05-17 09:51 -------
 I can still reproduce these issues using the attached repro's. Our 
 2.0 behavior does not match that of MS.
+
+------- Additional Comments From macite at gmail.com  2007-05-17 19:59 -------
+According to the release documentation Thread.Interrupt was
+implemented in 1.2.1, and the output indicates that the sleep is being
+interrupted... However I have installed the latest version, and
+retested the samples I have uploaded with the same result.
+
+The issue here is not that the Interrupt does not occur, but the fact
+that it does occur within the catch/finally blocks.


More information about the mono-bugs mailing list