[Mono-bugs] [Bug 54133][Cri] Changed - Thread.Abort is not implemented on windows.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 11 Feb 2004 20:39:02 -0500 (EST)

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


--- shadow/54133	2004-02-11 00:03:53.000000000 -0500
+++ shadow/54133.tmp.28973	2004-02-11 20:39:02.000000000 -0500
@@ -3,13 +3,13 @@
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: NEW   
 Severity: Unknown
-Priority: Blocker
+Priority: Critical
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: liyul@hotmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -194,6 +194,13 @@
 How to I quickly find out which EventHandler is killing me?
 ------- Additional Comments From liyul@hotmail.com  2004-02-11 00:03 -------
 Created an attachment (id=6668)
 the bug (trace, assemblies 100% mono-0.30 under windows 2000)
+------- Additional Comments From liyul@hotmail.com  2004-02-11 20:39 -------
+Thank you for let me know the Response.End could be using
+thread.Abort. Actually Response.Redirect seemed to trigger the bug,
+too. The xsp authtest\index.aspx failed with same sympton under
+windows. There should be ways of fixing it without using thread.Abort,
+though that may require changing the StateMachine.