[Mono-bugs] [Bug 76651][Maj] New - PC#4e, Chapter 18: Marshaling example crashes

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Nov 8 17:23:30 EST 2005


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 matt at use.net.

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

--- shadow/76651	2005-11-08 17:23:30.000000000 -0500
+++ shadow/76651.tmp.31058	2005-11-08 17:23:30.000000000 -0500
@@ -0,0 +1,45 @@
+Bug#: 76651
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: x86-64
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: matt at use.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: PC#4e, Chapter 18: Marshaling example crashes
+
+Please fill in this template when reporting a bug, unless you know what  
+you are doing.  
+Description of Problem:  
+  
+  
+Steps to reproduce the problem:  
+1. Download and unzip  
+http://www.libertyassociates.com/pages/files/ProgCSharp4eSourceR3.zip  
+2. cd ProgCSharp4eSourceR3/Chapter\ 18  
+3. gmcs -out:t.exe Marshaling/Marshaling/Marshaling.cs  
+4. mono ./t.exe  
+  
+Actual Results:  
+Unhandled Exception: System.IO.FileNotFoundException: Marshaling :  
+Marshaling  
+in (wrapper xdomain-invoke) System.AppDomain:CreateInstance  
+(string,string,bool,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo,object[],System.Security.Policy.Evidence)  
+in (wrapper remoting-invoke-with-check) System.AppDomain:CreateInstance  
+(string,string,bool,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo,object[],System.Security.Policy.Evidence)  
+in [0x00051] (at /home/matt/src/ProgCSharp4eSourceR3/Chapter  
+19/Marshaling/Marshaling/Marshaling.cs:121) Marshaling.Tester:Main ()  
+  
+Expected Results:  
+Should have same output as on MS.NET 2.0, which does not crash.  
+  
+How often does this happen?   
+ Every time.


More information about the mono-bugs mailing list