jrmrenegade wrote:

>
> I don't think that's it. I used "stdcall" in this case, which is
> correct for windows. Remember, the first callback worked. All the
> library had to do was call the same function back again, something
> that it had already done successfully, so the problem is occurring
> after the first callback and before the next one.

Because only after the first call the stack becomes corrupted? I'd
suggest you to try with a "cdecl" callback.


Dmitry