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

[bugzilla-daemon at bugzilla.ximian.com]

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.

http://bugzilla.ximian.com/show_bug.cgi?id=75683

--- shadow/75683	2005-08-02 03:02:43.000000000 -0400
+++ shadow/75683.tmp.13399	2005-08-02 03:02:43.000000000 -0400
@@ -0,0 +1,59 @@
+Bug#: 75683
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: interop
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: jankit at novell.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Summary: runtime does not handle a PInvoke calling conv = zero
+
+Description of Problem:
+
+If the calling convention for a PInvoke method is 0 (zero), then ms.net
+uses the platform default (basically it runs perfectly fine), but mono
+gives "unsupported calling convention". 
+
+
+** (tpi.exe:27900): WARNING **: unsupported calling convention
+
+** ERROR **: file loader.c: line 1456 (mono_method_signature_full): should
+not be reached
+aborting...
+Aborted
+
+
+The attached patch makes mono use MONO_CALL_DEFAULT if the calling conv is
+zero.
+
+Also, if the conv is anything other than the valid values or zero i.e., it
+is 0x600 or 0x700 then ms.net seems to just get hung, and mono gives the
+error mentioned earlier. Therefore, i dont think we need to change the
+behavior for these values.
+
+Also attached is a test case.
+
+
+Steps to reproduce the problem:
+1. ilasm test.il
+2. mono test.exe
+
+Actual Results:
+
+** (tpi.exe:27900): WARNING **: unsupported calling convention
+
+** ERROR **: file loader.c: line 1456 (mono_method_signature_full): should
+not be reached
+aborting...
+Aborted
+
+Expected Results:
+
+this is the source string