[Mono-bugs] [Bug 75683][Nor] Changed - runtime does not handle a PInvoke calling conv = zero

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Aug 2 10:17:26 EDT 2005

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by jankit at novell.com.


--- shadow/75683	2005-08-02 09:08:23.000000000 -0400
+++ shadow/75683.tmp.16808	2005-08-02 10:17:26.000000000 -0400
@@ -70,6 +70,16 @@
 ------- Additional Comments From vargaz at gmail.com  2005-08-02 09:08 -------
 0 is not a valid calling convention and the MS runtime probably handles
 it by accident. If you run PEverify on your test case, it correctly
 detects this. So I'm not sure we need to support this.
+------- Additional Comments From jankit at novell.com  2005-08-02 10:17 -------
+I found this while trying to compile samples bundled with Serge
+Lidin's book 'Inside Microsoft .NET IL Assembler'. And the call conv
+is missing from the pinvokeimpl in the samples.
+I compiled the program with ilasm .net 2.0 and that also emitted 0 as
+the calling conv, and peverify gives the same error AND it still runs
+it! But then yea, it could still be a bug with ms.net runtime.
+Anyway, what should be done in this case then?

More information about the mono-bugs mailing list