05-16-2006 10:13 AM
05-16-2006 10:20 AM
Uwe,
the problem you are describing sounds like a memory corruption to me. this can happen in your case most propably by two facts:
a) you use DLLs which corrupts the memory on their own affecting LV by it (can happen for instance with thread-unsave DLLs)
b) you create pointers to data within the DLLs which are passed back to LV but not handled properly there (e.g. closing them).
if i had to guess, i would more likely tend to possibility a).....
can you test the functionality of the functions from the DLLs not using LV? can you find out WHICH DLLcall creates the problem? if yes, did you try changing calling convetion/datatypes for the cll?
Norbert B.
05-16-2006 10:46 AM
05-17-2006 03:11 AM
Uwe,
there can be several reasons why calls do not work as intended. first of all the question:
is it always the same function that fails or does it change? Another question: Did you change the calling convetion as well (C/stdcall)? What about the parameters: is it possible that there are datatypes used which lead LV to the errors?
Theres something else you might to check: it sound a bit like LV gets messed up with the entry points of your DLLs. Is the information on the exported functions included in the DLL? When configuring the CLFN, do you see all exported functions immediatly?
Norbert B.
05-17-2006 05:30 AM
05-17-2006 11:21 AM