[Mono-dev] peverify vs mono --verify-all

[Rodrigo Kumpera]

peverify does verify everything eagerly and do very strict checks.

mono --verify-all disables some of the strict checks and does perform the
checking lazily only on what's executed.

Could you file a bug with your binary attached so I can take a look on
fixing this assert (I'm the author of this particular assert).

--
Rodrigo

On Fri, Sep 12, 2014 at 3:28 PM, mono user <mono.user789 at gmail.com> wrote:

> I would really appreciate help with this. I need to check that a dll I
> generated via reflection is correct, however peverify won't even start:
>
> [me at somewhere]$ peverify tmp.dll
> Could not load class with token 2000002
> * Assertion at class.c:5607, condition `!mono_loader_get_last_error ()'
> not met
>
> Aborted
>
> On the other hand,
>
> mono --verify-all --security=validil tmp.dll
>
> ponders things for a bit, then starts executing the dll file (it's really
> an executable).
>
> Could someone please tell me if the two commands should find the same
> problems  or not. Also, can I just take it that the dll is fine if the
> Microsoft implementation of peverify says so? Any hints on what to try to
> get the Mono implementation of peverify working would be especially helpful.
>
> I am using mono-3.10.0-branch because it fixes a problem manifesting
> itself with a triggered assertion inside mono (many thanks to Zoltan for
> the fix). I have seen similar behaviour under other recent versions of Mono.
>
>
>
>
>
>
>
> _______________________________________________
> 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/20140912/4281cd5a/attachment.html>