Compiling examples closes LabWindows/CVI

[ChrisSK]

I have a NI USB-5132 module, with NI-SCOPE 3.7.  I can bring up the device in "Measurement and Automation Explorer", and sees it as "Dev1".  I can bring up NI-Scope Soft Front Panel, and toggle the device, read whatever I want to read.  However, I'm trying to run on my CVI/LabWindows 2009 platform, but when I try to compile ANY of the examples, the development software closes.  No error message....nothing.  When I try to create a new DAQmx task, it sees no available devices for ANY of the possible measurements.  

Please help!  Otherwise, it would seem my work has purchased a very expensive method to click the exit button.

[Jackie_B]

Hi Chris, 

I'm sorry to hear that you are having so much trouble! Could you please provide some more details regarding when you experience this crash? Does this crash occur when you compile all programs or just specific ones? What examples are you attempting to compile? If this is the first time that you are compiling and are experiencing this issue, please refer to the following known bugs in CVI 2009

LabWindows™/CVI™ 2009 and 2009 SP1 Known Issues

• LabWindows/CVI may crash if compiling a project that includes LabWindows/CVI header files with a line containing the #pragma soft_reference statement
• Compiling a file with a syntax error can cause LabWindows/CVI to crash.

If these known bugs are not relevant to your code, can you please post a WinDbg log. The following explains how to do this. Despite this article being applied to LabVIEW, this is relevant for CVI as well.

Using WinDbg for LabVIEW Error Reporting

If you are running an operating system previous to Windows 7, please refer to the following: 

Description of the Dr. Watson for Windows (Drwtsn32.exe) Tool

I look forward to your response. Have a great day!

Regards,

Jackie

[ChrisSK]

Strangely enough, I did find a solution - I had to compile in RELEASE configuration.  For some reason, any of the examples or programs I've been writing referencing the High-Speed Digitizers WILL cause LabWindows/CVI to crash when trying to compile.  By compiling under the RELEASE configuration, the program compiles and links with no problems.  Go figure....I would like to know why exactly, but not too worried about it, since I was able to get my application up and running.

Attached is a zip of one of the mentioned examples that crashed LabWindows - again, only if run under Debug configuration.  If it's run under Release configuration, it compiles and executes without any problem.