I have recently been tinkering around with C# to C++ interop, in particularly setting up a callback function which is called from the C++ DLL.
namespace TomCSharpDLLImport
{
class Program
{
public delegate void TomDelegate(int a, int b);
[DllImport("TomDllNative.dll", CallingConvention = CallingConvention.Cdecl)]
public static extern void GetData();
[DllImport("TomDllNative.dll", CallingConvention = CallingConvention.Cdecl)]
public static extern void SetCallback(TomDelegate aCallback);
static void Main(string[] args)
{
TomDelegate lTD = new TomDelegate(Program.TomCallback);
SetCallback(lTD); //Sets up the callback
int thread = Thread.CurrentThread.ManagedThreadId;
GetData(); //This calls the callback in unmanaged code
while (true) ;
}
//Callback function which is called from the unmanaged code
public static void TomCallback(int a, int b)
{
Console.WriteLine("A: {0} B: {1}", a, b);
int thread = Thread.CurrentThread.ManagedThreadId;
}
}
}
The question I have is that, when the program control comes into the TomCallback function, I was expecting it to then hit the while(true) loop in Main. However instead the program just exits. I can't quite get my head round the behaviour, part of me imagines this is as expected but part of me would have expected it to continue on in main.
What I was expecting...
However this is not quite right.
Would someone be kind enough to explain what happens.
In order to save space I haven't posted the unmanaged code, however if it is needed i'm happy to post
Edit: I turned on Unmanaged debugging (totally forgot to do this) and now I see the crash..
Run-Time Check Failure #0 - 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.
Native code as this is where crash is
#include "stdafx.h"
typedef void (*callback_function)(int, int);
extern "C" __declspec(dllexport) void SetCallback(callback_function aCallback);
extern "C" __declspec(dllexport) void GetData();
callback_function gCBF;
__declspec(dllexport) void SetCallback(callback_function aCallback)
{
gCBF = aCallback;
}
__declspec(dllexport) void GetData()
{
gCBF(1, 2);
}
C programming language is a machine-independent programming language that is mainly used to create many types of applications and operating systems such as Windows, and other complicated programs such as the Oracle database, Git, Python interpreter, and games and is considered a programming foundation in the process of ...
Compared to other languages—like Java, PHP, or C#—C is a relatively simple language to learn for anyone just starting to learn computer programming because of its limited number of keywords.
What is C? C is a general-purpose programming language created by Dennis Ritchie at the Bell Laboratories in 1972. It is a very popular language, despite being old. C is strongly associated with UNIX, as it was developed to write the UNIX operating system.
In the real sense it has no meaning or full form. It was developed by Dennis Ritchie and Ken Thompson at AT&T bell Lab. First, they used to call it as B language then later they made some improvement into it and renamed it as C and its superscript as C++ which was invented by Dr.
You must convert your managed callback to the Native Function Pointer (IntPtr in C#) by using the
IntPtr Marshal.GetFunctionPointerForDelegate(Delegate d)
method.
Your usage of SetCallback() with System.Delegate as an argument is wrong.
Make it
SetCallback(Marshal.GetFunctionPointerForDelegate(lTD));
and redeclare SetCallback as
/// StdCall is crucial here
[DllImport("TomDllNative.dll", CallingConvention = CallingConvention.StdCall)]
public static extern void SetCallback(IntPtr aCallback);
I had the exact same problem as the OP (same error message). The accepted answer did not help at all, which even @TomP89 admits in the comments.
This is not surprising because the error message indicates that the calling convention of the passed callback function is wrong, whereas the supposed solution changes the calling convention of the function that passes the callback, which results in a stack imbalance if what the library exports are cdecl-functions (as is the default case for all functions outside the Win32 API).
It turns out that .Net assumes by default the calling convention "stdcall" for any delegate. Typically the unmanaged code will assume the same calling convention as its exported functions (in this case and mine: "cdecl").
So the true solution (which finally worked for me) is changing the calling convention of the callback to "cdecl". This question shows how this is accomplished, in short:
[UnmanagedFunctionPointer(CallingConvention.Cdecl)]
public delegate void TomDelegate(int a, int b);
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With