[Mono-bugs] [Bug 35004][Blo] New - Unhandled Exception: System.Reflection.AmbiguousMatchException: <element> has more than one attribute of type <attribute_type>

[bugzilla-daemon@rocky.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 james.birmingham@corp.terralycos.com.

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

--- shadow/35004	Tue Dec  3 18:47:54 2002
+++ shadow/35004.tmp.32173	Tue Dec  3 18:47:54 2002
@@ -0,0 +1,88 @@
+Bug#: 35004
+Product: Mono/MCS
+Version: unspecified
+OS: Red Hat 7.2
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Blocker
+Component: Misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: James.Birmingham@corp.terralycos.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Unhandled Exception: System.Reflection.AmbiguousMatchException: <element> has more than one attribute of type <attribute_type>
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+When compiling my C# application I consistently get the following crash 
+dump:
+
+Unhandled Exception: System.Reflection.AmbiguousMatchException: <element> 
+has more than one attribute of type <attribute_type>
+in <0x00045> 00 System.Attribute:FindAttribute (object[])
+in <0x00049> 00 System.Attribute:GetCustomAttribute 
+(System.Reflection.MemberInfo,System.Type,bool)
+in <0x0019e> 00 Mono.CSharp.TypeManager:IndexerPropertyName (System.Type)
+in <0x0007a> 00 Mono.CSharp.Indexers:GetIndexersForTypeOrInterface 
+(System.Type,System.Type)
+in <0x00084> 00 Mono.CSharp.Indexers:GetIndexersForType 
+(System.Type,System.Type,Mono.CSharp.Location)
+in <0x0007e> 00 Mono.CSharp.IndexerAccess:DoResolve 
+(Mono.CSharp.EmitContext)
+in <0x0014a> 00 Mono.CSharp.Expression:Resolve 
+(Mono.CSharp.EmitContext,Mono.CSharp.ResolveFlags)
+in <0x00146> 00 Mono.CSharp.ElementAccess:DoResolve 
+(Mono.CSharp.EmitContext)
+in <0x0014a> 00 Mono.CSharp.Expression:Resolve 
+(Mono.CSharp.EmitContext,Mono.CSharp.ResolveFlags)
+in <0x00025> 00 Mono.CSharp.Binary:DoResolve (Mono.CSharp.EmitContext)
+in <0x0014a> 00 Mono.CSharp.Expression:Resolve 
+(Mono.CSharp.EmitContext,Mono.CSharp.ResolveFlags)
+in <0x0005a> 00 Mono.CSharp.CompoundAssign:DoResolve 
+(Mono.CSharp.EmitContext)
+in <0x0014a> 00 Mono.CSharp.Expression:Resolve 
+(Mono.CSharp.EmitContext,Mono.CSharp.ResolveFlags)
+in <0x0001d> 00 Mono.CSharp.StatementExpression:Resolve 
+(Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x00260> 00 Mono.CSharp.For:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x000a2> 00 Mono.CSharp.If:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x000ad> 00 Mono.CSharp.Try:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x00257> 00 Mono.CSharp.Block:Resolve (Mono.CSharp.EmitContext)
+in <0x00104> 00 Mono.CSharp.EmitContext:EmitTopBlock 
+(Mono.CSharp.Block,Mono.CSharp.InternalParameters,Mono.CSharp.Location)
+in <0x0056c> 00 Mono.CSharp.MethodData:Emit 
+(Mono.CSharp.TypeContainer,Mono.CSharp.Block,object)
+in <0x00023> 00 Mono.CSharp.Method:Emit (Mono.CSharp.TypeContainer)
+in <0x00291> 00 Mono.CSharp.TypeContainer:Emit ()
+in <0x004de> 00 Mono.CSharp.RootContext:EmitCode ()
+in <0x00736> 00 Mono.CSharp.Driver:MainDriver (string[])
+in <0x0000f> 00 Mono.CSharp.Driver:Main (string[])
+
+Steps to reproduce the problem:
+The application consists of 100+ files so isolating the problem will be 
+diffcult.  I can provide a zip of the source code if needed.  Hopefully 
+just looking at the stack trace will be enough to understand the problem.
+
+Actual Results:
+
+
+Expected Results:
+
+
+How often does this happen? 
+Every time.
+
+Additional Information: