[Mono-list] Portable.Net and Mono?

Fri, 7 Feb 2003 08:51:46 -0800

Gthanks for the hint with PEVerify .... It creates 10 errors:

e:\>PEVerify.exe libc64.dll

[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x0200000A]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x0200000B]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x0200000C]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x0200000D]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x0200000E]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x0200000F]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x02000010]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x02000013]
[MD]: Error: Extraneous bits in Flags (0x00000040). [token:0x02000016]
[MD]: Error: Token 0x02000005 following ELEMENT_TYPE_CLASS (_VALUETYPE) in signature is a ValueType (Class,respectively). [token:0x06000011]
10 Errors Verifying libc64.dll

So it is not a Mono problem :)

-- Carsten

-----Original Message-----
From: Paolo Molaro [mailto:lupus@ximian.com] 
Sent: February 07, 2003 11:41 AM
To: mono-list@ximian.com
Subject: Re: [Mono-list] Portable.Net and Mono?

On 02/07/03 carsten.hess@autodesk.com wrote:
> Now here is a question that I am wondering about:
> What is the a relationship between Portable.Net and Mono?

This has been discussed on the list already, check the archives. pnet is a different project that shares some of the same goals as 
mono, but with different technical decisions. Sometimes the two projects cooperate, sharing code etc.

> Also, do you think that theoretically I should be able to compile
> code in Portable.Net (e.g. C-Code compiled by cscc) and run it 
> under Mono?
> Initial test of mine show that mono doesn't' like the libc64.dll.
> Disassembling libc64.dll creates the following error 
> 
> error in file_loader.c: line 332 :(Method_in_member_ref): should not 
> be reached.

I guess this is simple to fix, it probably uses a MEMBERREF_PARENT_TYPEDEF 
coded index. I'll commit a fix for that.

> If it should be running fine, I see whether I can find and fix the 
> bug(s). But I thought I
> check first on whether this is even supposed to work.

If the assemblies follow the standard CLI specs, they should work with mono (barring bugs and unimplemented features, of course). A quick way to check is using the PEVerify tool from the ms SDK, if you have access to a windows machine: if you get errors the assemblies probably don't follow the spec (though you need to check for unsafe code usage or other errors).

lupus

-- 
-----------------------------------------------------------------
lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better
_______________________________________________
Mono-list maillist  -  Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list