[Mono-bugs] [Bug 77921][Nor] New - mcs generates invalid IL in nunit.util assembly

[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 gert.driesen at pandora.be.

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

--- shadow/77921	2006-03-26 10:06:09.000000000 -0500
+++ shadow/77921.tmp.17926	2006-03-26 10:06:09.000000000 -0500
@@ -0,0 +1,38 @@
+Bug#: 77921
+Product: Mono: Compilers
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: C#
+AssignedTo: rharinath at novell.com                            
+ReportedBy: gert.driesen at pandora.be               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mcs generates invalid IL in nunit.util assembly
+
+Apparently, mcs generates invalid IL in the nunit.util assembly for NUnit 
+2.3.6078.
+
+Running NUnit built on Mono, on MS.NET generates a CLR error.
+
+Not sure if this is the reason why the NUnit built by mcs does not run on 
+MS.NET, but peverify reports the following errors for nunit.util.dll:
+
+[IL]: Error: [c:\nunit-test\nunit.util.dll : 
+NUnit.Util.TestLoader::CreateRunner] [offset 0x0000001A] [opcode stloc.0] 
+[found objref 'NUnit.Core.LongLivingMarshalByRefObject'] [expected 
+objref 'NUnit.Util.TestRunnerEx'] Unexpected type on the stack.
+
+To reproduce:
+
+1. Extract the attached (gzipped tar) archive.
+2. Change to the extracted directory.
+3. Run make
+4. Copy nunit.util.dll to a Windows box containing the .NET Framework SDK 
+and run peverify on it.