[Mono-bugs] [Bug 75126][Nor] New - crash when running a binary generated with MS.NET 2.0 beta 2

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Jun 2 15:31:24 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 matt.hargett at logiclibrary.com.

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

--- shadow/75126	2005-06-02 15:31:24.000000000 -0400
+++ shadow/75126.tmp.13932	2005-06-02 15:31:24.000000000 -0400
@@ -0,0 +1,85 @@
+Bug#: 75126
+Product: Mono: Runtime
+Version: 1.1
+OS: SLES 9
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: interop
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: matt.hargett at logiclibrary.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: crash when running a binary generated with MS.NET 2.0 beta 2
+
+Description of Problem:
+Trying to run FxCop from VSTS 2005 beta 2 yields a NotSupportedException: 
+"This .resources file requires unsupported set class version: 2"
+
+Steps to reproduce the problem:
+1. Copy the entire FxCop directory from VSTS 2005 beta 2
+(C:\Program Files\Microsoft Visual Studio 8\Team Tools\Static Analysis
+Tools\FxCop)
+2. Using current subversion head:
+matt at surfboard:~/FxCop> mono FxCopCmd.exe
+
+
+Actual Results:
+Crash.
+
+Unhandled Exception: System.Reflection.TargetInvocationException: Exception
+has been thrown by the target of an invocation. --->
+System.NotSupportedException: This .resources file requires unsupported set
+class version: 2
+in <0x00265> System.Resources.ResourceReader:ReadHeaders ()
+in <0x000c5> System.Resources.ResourceReader:.ctor (System.IO.Stream stream)
+in <0x00050> System.Resources.ResourceSet:.ctor (System.IO.Stream stream)
+in <0x00000> <unknown method>
+in (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke
+(object,object[])
+in <0x000af> System.Reflection.MonoCMethod:Invoke (System.Object obj,
+BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[]
+parameters, System.Globalization.CultureInfo culture)--- End of inner
+exception stack trace ---
+
+in <0x0014b> System.Reflection.MonoCMethod:Invoke (System.Object obj,
+BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[]
+parameters, System.Globalization.CultureInfo culture)
+in <0x0003e> System.Reflection.MonoCMethod:Invoke (BindingFlags invokeAttr,
+System.Reflection.Binder binder, System.Object[] parameters,
+System.Globalization.CultureInfo culture)
+in <0x00048> System.Reflection.ConstructorInfo:Invoke (System.Object[]
+parameters)
+in <0x001e0> System.Activator:CreateInstance (System.Type type,
+System.Object[] args, System.Object[] activationAttributes)
+in <0x00031> System.Activator:CreateInstance (System.Type type,
+System.Object[] args)
+in <0x002e5> System.Resources.ResourceManager:InternalGetResourceSet
+(System.Globalization.CultureInfo culture, Boolean Createifnotexists,
+Boolean tryParents)
+in <0x005e4> System.Resources.ResourceManager:InternalGetResourceSet
+(System.Globalization.CultureInfo culture, Boolean Createifnotexists,
+Boolean tryParents)
+in <0x000e2> System.Resources.ResourceManager:GetString (System.String
+name, System.Globalization.CultureInfo culture)
+in <0x0002d> Microsoft.Tools.FxCop.Command.Localized:get_ToolName ()
+in <0x00678> Microsoft.Tools.FxCop.Command.FxCopCommand:Main
+(System.String[] args)
+
+
+
+Expected Results:
+Preferrably, FxCop's commandline interface should just run since it appears
+to be 100% managed. At the very least mono should not crash, and give a
+nicer error about .NET 2.0 binaries being unsupported.
+
+How often does this happen? 
+Every time.
+
+Additional Information:
+FxCop 1.312 for .NET 1.1 has a different error, I'm writing a different bug
+for that.


More information about the mono-bugs mailing list