MATLAB: Do I receive a calling convention error when calling a Fortran function from a C S-Function with Simulink

cmsvcsimulink

I have a legacy Fortran function that I am using from Simulink via a S-Function wrapper. When I debug it using Visual Studio, MSVC gives me the following error about calling conventions.

 Debug Error!
 The value of ESP was not properly saved across a function call. This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention.

Best Answer

The error message indicates that there is a calling convention mismatch.

A workaround is to try placing a __stdcall or __fastcall statement (depending on the compiler) between the "extern type" and the function name in the function prototype in the c-file.

Related Solutions

MATLAB: Do I get a runtime error concerning the “ESP” register when attempting to call a MEX-file from a C++-based test harness

This issue stems from your use of the CALLBACK macro. This is a macro for the STDCALL calling convention, but MEX-files always use the CDECL convention. This conflict leads to the runtime error.

You should be able to resolve this issue by using:

 typedef void (*LPFNDLLFUNC1)(int, mxArray**, int, mxArray**);

instead of

 typedef void (CALLBACK* LPFNDLLFUNC1)(int, mxArray**, int, mxArray**);

MATLAB: Angle2dcm convention

It is a question of the view point: The rotation matrix can rotate the object or the coordinate system. As you mentioned already, the conventions are different in e.g. space craft and biomechanics.

Best Answer

Related Solutions

MATLAB: Do I get a runtime error concerning the “ESP” register when attempting to call a MEX-file from a C++-based test harness

MATLAB: Angle2dcm convention

Related Question