[Mono-bugs] [Bug 553403] [verifier] abort in mono_get_delegate_invoke on bad assembly

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Nov 24 16:25:49 EST 2009



Sebastien Pouliot <spouliot at novell.com> changed:

           What    |Removed                     |Added
            Summary|[verifier] abort in         |[verifier] abort in
                   |:mono_get_delegate_invoke   |mono_get_delegate_invoke on
                   |on bad assembly             |bad assembly

--- Comment #1 from Sebastien Pouliot <spouliot at novell.com> 2009-11-24 21:25:46 UTC ---
another identical case (not attached, with a stack trace)

** ERROR:(object.c:3144):mono_get_delegate_invoke: assertion failed: (im)
[New Thread 0x7ff5db996710 (LWP 20192)]

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7ff5db996710 (LWP 20192)]
0x00007ff5da5035c5 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ff5da5035c5 in raise () from /lib64/libc.so.6
#1  0x00007ff5da504bb3 in abort () from /lib64/libc.so.6
#2  0x00007ff5db3312c7 in g_assertion_message () from
#3  0x00007ff5db331762 in g_assertion_message_expr () from
#4  0x000000000045fb55 in mono_get_delegate_invoke (klass=0x8dfae8) at
#5  0x000000000049b865 in mono_method_verify (method=<value optimized out>,
level=<value optimized out>) at verify.c:2943
#6  0x000000000040daed in main (argc=8430352, argv=<value optimized out>) at

It looks like mono_get_delegate_invoke callers (about 15 of them) should check
for NULL (and, worse case scenario, assert). That would leave
verify_delegate_compatibility (inlined in the previous stack trace) able to
call ADD_VERIFY_ERROR and fail correctly.

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