[Mono-bugs] [Bug 78652][Maj] New - Control.BeginInvoke crashes in .net 2.0 profile if security not enabled.

[bugzilla-daemon at bugzilla.ximian.com]

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 tilps.kilm at gmail.com.

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

--- shadow/78652	2006-06-15 07:19:13.000000000 -0400
+++ shadow/78652.tmp.1186	2006-06-15 07:19:13.000000000 -0400
@@ -0,0 +1,31 @@
+Bug#: 78652
+Product: Mono: Class Libraries
+Version: 1.1
+OS: Debian Woody
+OS Details: Debian Sid
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: Windows.Forms
+AssignedTo: peter at novonyx.com                            
+ReportedBy: tilps.kilm at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Control.BeginInvoke crashes in .net 2.0 profile if security not enabled.
+
+Description of Problem:
+Control.BeginInvokeInternal sets the asyncMethodData.context regardless of
+whether security is enabled.  But if security is not enabled, the security
+context within the execution context does not have its CompressedStack
+setup, therefore using the ExecutionContext.Run method results in a null
+argument exception when it calls SecurityContext.Run which calls
+CompressedStack.Run.
+
+Now, either ExecutionContext should be checking wheter security is set, and
+then performing special handling, or BeginInvokeInternal should.
+
+I chose the later, as 1.1 profile is already checking whether security is
+set. (Patch attached...)