[Mono-bugs] [Bug 75988][Nor] New - monop aborts with error on FxCop bins from VS2005

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

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

--- shadow/75988	2005-09-05 10:50:45.000000000 -0400
+++ shadow/75988.tmp.14881	2005-09-05 10:50:45.000000000 -0400
@@ -0,0 +1,59 @@
+Bug#: 75988
+Product: Mono: Tools
+Version: 1.1
+OS: 
+OS Details: gentoo amd64
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: monop
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: matt at use.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: monop aborts with error on FxCop bins from VS2005
+
+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. from VSTS2005 beta2, copy the "Microsoft Visual Studio 8\Team  
+Tools\Static Analysis Tools\FxCop\" dir to a mono machine  
+2. run "monop -r:FxCopCmd.exe"  
+  
+Actual Results:  
+warnings and then a hard error. no information about the assembly is  
+printed.  
+  
+matt at geoff-linux ~/bin $ ./monop -r:FxCop/FxCopCmd.exe  
+  
+Assembly Information:  
+  
+** (/home/matt//lib/mono/1.0/monop.exe:2602): WARNING **: TypeRef  
+ResolutionScope not yet handled (39)  
+  
+** (/home/matt//lib/mono/1.0/monop.exe:2602): WARNING **: The class  
+DebuggingModes could not be loaded, used  
+in /home/matt/bin/FxCop/FxCopCmd.exe (token 0x01000028)  
+  
+** (/home/matt//lib/mono/1.0/monop.exe:2602): WARNING **: Missing  
+method .ctor in assembly /home/matt/bin/FxCop/FxCopCmd.exe, type  
+DebuggableAttribute  
+  
+** ERROR **: Can't find custom attr constructor  
+image: /home/matt/bin/FxCop/FxCopCmd.exe mtoken: 0x0a000018  
+aborting...  
+Aborted  
+  
+  
+Expected Results:  
+should run so I can debug issues with this binary on linux/mono without  
+switching to/from ildasm  
+  
+How often does this happen?   
+every time