[Mono-bugs] [Bug 47847][Nor] Changed - LogicalCallContext created at wrong time in MethodCallMessage

[bugzilla-daemon@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 lluis@ximian.com.

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

--- shadow/47847	2003-08-23 16:48:46.000000000 -0400
+++ shadow/47847.tmp.369	2003-08-24 06:26:16.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 47847
 Product: Mono/Runtime
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: vladimir@pobox.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -64,6 +64,16 @@
 --- end ---
 
 ------- Additional Comments From vladimir@pobox.com  2003-08-23 16:48 -------
 Created an attachment (id=5197)
 LogicalCallContext creation patch
 
+
+------- Additional Comments From lluis@ximian.com  2003-08-24 06:26 -------
+I just realized that the CallContext should be restored before leaving
+PrivateInvoke. This can be done like this:
+
+if (res_msg.LogicalCallContext != null)
+CallContext.SetCurrentCallContext (res_msg.LogicalCallContext);
+
+In any case, the patch is ok. Feel free to commit.
+Thanks!