[Mono-bugs] [Bug 77134][Nor] New - Problem with events in generic classes.

[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 latexer at gentoo.org.

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

--- shadow/77134	2005-12-31 18:23:16.000000000 -0500
+++ shadow/77134.tmp.14137	2005-12-31 18:23:16.000000000 -0500
@@ -0,0 +1,38 @@
+Bug#: 77134
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: Gentoo Linux
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: latexer at gentoo.org               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Problem with events in generic classes.
+
+There seems to be a runtime problem with events in generic classes. Generic
+classes seem to be generated properly, but the runtime seems unable to
+actually find the event for the class after that. As a result gmcs spits
+some odd errors about the visibility of the event, etc usually, which is
+actually a result of the generated backing field being the only item with
+the name found for the class, e.g. class Foo<T> has an event "Ev", which
+results in the event and the field "Ev" created, but only the private field
+"Ev" is seen by the compiler, so it warns about it not being visible.
+
+I will attach a small tarball that demonstrates the problem, with both the
+non-generic and generic classes. monodis seems to show everything generated
+properly for the classes. One works compiled with gmcs, one doesn't. This
+has been tested both with mono-1.1.10.1 and mono-1.1.12.1. I've not had a
+chance to test with SVN mono.
+
+In trying to debug this, I think I tracked down the problem to
+mono/metadata/metadata.c:3448 in the function
+mono_metadata_events_from_typedef. The bsearch seems to fail, so no table
+indexes are returned. I don't know the runtime internals well enough to
+even begin to ponder *why* this might be the case, how to debug further, etc.