Using Qlibrary on a function that uses arguments

[wysota]

Is the application multithreaded?

[schall_l]

Yes, the function in which the DLL is accessed runs within a thread.
But I don't understand how this can affect how filling a simple QString can behave differently before and after the DLL function is called.
I have attached a demo project, including the DLL, in a previous post, that can be used to reproduce the strange behavior I am observing, so that you can have a look if you want.

[wysota]

Maybe the function is not reentrant?

[schall_l]

I've got the answer from the Trolltech support.

I negliged the windows calling convention (cf article at http://www.unixwiz.net/techtips/win32-callconv.html) with the consequence of corrupts memory all over the place.

Finally I had to change my typedef from:

typedef short int (*GetInfo)(unsigned char,unsigned char,unsigned char *,unsigned char *,unsigned char *,unsigned char *);

typedef short int (*GetInfo)(unsigned char,unsigned char,unsigned char *,unsigned char *,unsigned char *,unsigned char *);

To copy to clipboard, switch view to plain text mode 

into:

typedef short int (__stdcall *GetInfo)(unsigned char,unsigned char,unsigned char *,unsigned char *,unsigned char *,unsigned char *);

typedef short int (__stdcall *GetInfo)(unsigned char,unsigned char,unsigned char *,unsigned char *,unsigned char *,unsigned char *);

To copy to clipboard, switch view to plain text mode 

That solved everything.