[Mono-bugs] [Bug 553306] [verifier] SIGSEGV in mono_class_init on a bad assembly

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Nov 23 20:47:38 EST 2009


http://bugzilla.novell.com/show_bug.cgi?id=553306

http://bugzilla.novell.com/show_bug.cgi?id=553306#c3


--- Comment #3 from Sebastien Pouliot <spouliot at novell.com> 2009-11-24 01:47:33 UTC ---
> I think the problem is somewhere else, klass should be set every time AFAIU.

Either NULL is a valid value (like the patch fix) or not (i.e. the caller is
abusing API). I don't mind which one wins as long as it does not crash. FWIW
both NULL uses looks recent (r139974 and r140109) and from you ;-)

> Which piece of code set the loader error on this case?

You mean source-wise (below) or a test case (binary attached) ?

[mono] ~/svn/branches/2-6/mono @ grep mono_loader_set_error_field_load
mono/metadata/*.c
mono/metadata/loader.c: * mono_loader_set_error_field_load:
mono/metadata/loader.c:mono_loader_set_error_field_load (MonoClass *klass,
const char *member_name)
mono/metadata/loader.c:        mono_loader_set_error_field_load (NULL, fname);
mono/metadata/loader.c:            mono_loader_set_error_field_load (NULL,
fname);
mono/metadata/loader.c:        mono_loader_set_error_field_load (klass, fname);

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list