---- Reported by grompf@sublimeintervention.com 2004-12-14 14:12:35 MST ----

Calling a Response.Redirect is creating a SIGILL on PPC on XSP/Mono HEAD currently.

This bug may go -> runtime; however I think it might be dealing with some of the recent 
threading/sys.web changes.

The following callback registered to a button:

void Clicked (object o, EventArgs e)
{
                Response.Redirect ("/index.aspx");
}

Will cause the sigill (XSP and XSP2);

If I try / catch around that block I get:

Application_Start
System.Threading.ThreadAbortException: Thread was being aborted
in <0x0008c> (wrapper managed-to-native) System.Object:
__icall_wrapper_mono_thread_interruption_checkpoint ()
in <0x000b4> (wrapper managed-to-native) System.Threading.Thread:Abort_internal (object)
in <0x00028> System.Threading.Thread:Abort (object)
in <0x0007c> System.Web.HttpResponse:End ()
in <0x00134> System.Web.HttpResponse:Redirect (string,bool)
in <0x0002c> System.Web.HttpResponse:Redirect (string)
in <0x000dc> ASP.session1_aspx:Clicked (object,System.EventArgs)

System.Threading.ThreadAbortException: Thread was being aborted
in <0x0016c> System.Web.UI.Page:ProcessRequest (System.Web.HttpContext)
in (unmanaged) (wrapper xdomain-dispatch) Mono.ASPNET.XSPApplicationHost:ProcessRequest 
(object,byte[]&,byte[]&,int,long,int,long,int,string,string,string,string,string,byte[],string)
in <0x00114> (wrapper xdomain-dispatch) Mono.ASPNET.XSPApplicationHost:ProcessRequest 
(object,byte[]&,byte[]&,int,long,int,long,int,string,string,string,string,string,byte[],string)
in <0x002dc> (wrapper xdomain-invoke) Mono.ASPNET.XSPApplicationHost:ProcessRequest 
(int,long,int,long,int,string,string,string,string,string,byte[],string)
in <0x0017c> (wrapper remoting-invoke-with-check) Mono.ASPNET.XSPApplicationHost:
ProcessRequest (int,long,int,long,int,string,string,string,string,string,byte[],string)
in <0x005e0> Mono.ASPNET.XSPWorker:Run (object)

-kangaroo



---- Additional Comments From grompf@sublimeintervention.com 2004-12-14 14:15:56 MST ----

Further note;

If I use Response.Redirect ("/index.aspx", false) the code redirects fine (this probably 
causes a leak tho does it not?)

-kangaroo




---- Additional Comments From gonzalo@ximian.com 2004-12-14 17:19:45 MST ----

Moving this to the runtime, as it works on x86



---- Additional Comments From grompf@sublimeintervention.com 2004-12-14 23:34:35 MST ----

I'm renaming this bug as I've managed to drill down a real test case to PPC improper 
exception handling.

Test case attached below.

-kangaroo




---- Additional Comments From grompf@sublimeintervention.com 2004-12-14 23:35:09 MST ----

Created an attachment (id=167167)
testcase




---- Additional Comments From grompf@sublimeintervention.com 2005-09-06 21:52:42 MST ----

lupus,

  It appears that this is fixed?  Did I miss something or does the new io-layer with aborts just 
mask this now?

-kangaroo




---- Additional Comments From miguel@ximian.com 2006-07-20 20:07:02 MST ----

I can not see this bug, am adding a test case though.

Imported an attachment (id=167167)

Unknown operating system unknown. Setting to default OS "Other".