LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem running in debug mode

I Wrote an application that exchange data with my HW via telnet ( Distinct Telnet DLL ).
The application worked good when I used WIN NT4 both in debug & Release mode, But since I installed LW on my new PC with WIN2000 I have problems debuging my application, the Telnet DLL is not working ( error Msg from DLL ). the application works without problems when execution (CTRL + F5 ) the application, problems are only when Debuging ( SHIFT + F5 ).
is it concern in stuck size or somting ?
what can be the problem ?
0 Kudos
Message 1 of 3
(3,164 Views)
Shimon,

It's not common that an application works fine in release mode and does not work in debugging. There are many different possibilities, you can try changing the size of the stack in Options>>Build options. If you built the dll the you can probably track the error down. Another thing to make sure is that you are using the right calling convention, it is possible that CVI in debug mode detects that the calling convention is incorrect, but in debug mode this is neglected.

Do you know in what language was the DLL developed?

Keep me updated!

Juan Carlos
National Instruments
0 Kudos
Message 2 of 3
(3,164 Views)
Juan,

The Thing is that this application worked fine in both compilation mode when i worked under WIN NT4, all the problems started when I changed to WIN2000.

I purchased the DLL from Distinct ( VIT 5 )and i am positive that I am using it correctly.

what is the meaning of stuck size, current value is 250000 Byte ( default setting ), should it be bigger ?

Regards

Shimon Kringel
0 Kudos
Message 3 of 3
(3,164 Views)