[Mono-bugs] [Bug 75277][Blo] New - Issue with 'ref' argument in remoting context

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Jun 15 12:52:56 EDT 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 joannes.vermorel at ens.fr.


--- shadow/75277	2005-06-15 12:52:56.000000000 -0400
+++ shadow/75277.tmp.18068	2005-06-15 12:52:56.000000000 -0400
@@ -0,0 +1,55 @@
+Bug#: 75277
+Product: Mono: Class Libraries
+Version: 1.1
+OS: Red Hat 9.0
+OS Details: 
+Status: NEW   
+Priority: Blocker
+Component: CORLIB
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: joannes.vermorel at ens.fr               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Issue with 'ref' argument in remoting context
+I have a DLL containing NUnit tests that succeed on WinXP .Net 1.1 and
+fails against mono (most recent SVN build). The problem seems to be related
+to the serialization/deserialization of IMessage's that are targeting
+methods with 'ref' arguments.
+===== Steps to reproduce the problem =====
+1. Download "NGrid.Rosette-v0.1.2.zip" from
+2. Unzip the archive. 
+3. Run unit tests from NUnit console 
+$ mono nunit-console.exe NGrid.Rosette.dll
+===== Actual Results: ====
+Tests run: 1, Failures: 1, Not run: 0, Time: 17.200242 seconds
+1) NGrid.Rosette.HubServices+Tests.AllTests : #A00 Argument expected,
+should not be null.
+// This assertion is contained in NGrid.Core.dll, the method is
+// NGrid.Collections.GPipeline.Tests.ComputationValidity
+===== Expected Results =====
+Do not pay attention to the large amount of trace lines. The tests require
+about 15s to be run. At the end, there should be a NUnit message indicating
+that the tests have succeed.
+There is also a System.CannotUnloadAppDomainException that is thrown. This
+is an independent bug, filled here
+(this exception is not related to the current problem).
+===== How often does this happen? =====
+===== Additional Information =====
+I am running mono on an AMD64 machine (64b OS).

More information about the mono-bugs mailing list