[Mono-dev] How do I avoid these assertions?

Zoltan Varga vargaz at gmail.com
Fri Sep 5 19:31:35 UTC 2014


  The mini.c:4656 assertion is a runtime bug, it happens when a method
becomes too large.


On Fri, Sep 5, 2014 at 1:40 PM, mono user <mono.user789 at gmail.com> wrote:

> Could somebody please tell me what might be triggering the assertions
> below? They happen when I generate my own IL. While the same IL works fine
> under .net, it could still be that I am doing something wrong because .net
> tends to be more forgiving than the spec requires.
> * Assertion at mini.c:4175, condition `code' not met
> * Assertion at mini.c:4656, condition `cfg->code_size - cfg->epilog_begin
> < 0xffff' not met
> On a related note, how do I run peverify please? I always seem to get the
> following. The code runs fine (which seems to suggest the libraries are
> available, which in turn seems to be the main reason for why it doesn't
> work for others who ask about it in places Google can see). I think the
> assertions might just go away if I fix whatever is reported by peverify.
> Having said that, the .net version of peverify says everything is fine.
> peverify /CLOCK /VERBOSE tmp.exe
> Could not load class with token 2000002
> * Assertion at class.c:5600, condition `!mono_loader_get_last_error ()'
> not met
> Many thanks.
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140905/8d3f4c99/attachment-0001.html>

More information about the Mono-devel-list mailing list