选择ctypes的DLL加载机制：调用约定错误排查与修复

I recently ran into a frustrating issue with ctypes while calling a DLL function, and wanted to share the fix since it tripped me up even though others didn't hit the same problem.

The Problem #

I started with this code to load my DLL:

U2_C_INTERFACE = ctypes.cdll.LoadLibrary("mydllname")

This worked perfectly on my colleague's Windows 10 machine and several other test devices, but on my own system, every call to a DLL method threw this error:

Procedure called with not enough arguments (24 bytes missing) or wrong calling convention

Why This Happens #

The root cause is a mismatched calling convention:

• ctypes.cdll uses the cdecl calling convention by default. In this setup, the caller cleans up the stack after the function call.
• Many Windows DLLs (especially those following standard Windows API patterns) are compiled using the stdcall convention. Here, the function itself cleans up the stack before returning.

When these don't match, the stack gets corrupted, leading to the "missing arguments" error even if you passed the right number of parameters.

The Fix #

Switching to ctypes.windll (or ctypes.WinDLL) fixes the issue immediately, since it uses the stdcall convention by default:

U2_C_INTERFACE = ctypes.windll.LoadLibrary("mydllname")
# Or equivalently:
# U2_C_INTERFACE = ctypes.WinDLL("mydllname")

After making this change, all DLL method calls worked as expected on my machine, matching the behavior on other devices.

A Quick Note #

If you have control over the DLL's source code, you could also explicitly set the calling convention to cdecl to match cdll. But for most pre-built Windows DLLs, sticking with windll is the safer bet.

内容的提问来源于stack exchange，提问作者Héctor C.