LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot compile project in CVI 2009 that was previously opened in CVI 2010

Solved!
Go to solution

This has been extremely irrititating and cannot figure out what the heck is happening.  I have a computer with CVI 2010 and a sepearate one with CVI 2009.

 

i have a project and cws that was created in 2009.

 

i have opened it and recompiled things in CVI 2010 since then, making sure I saved my .uir file in a 2009 or earlier CVI version.

 

I can usually open the .prj or .cws file back on my CVI 2009 computer, but when trying to compile and run in debug mode, all of CVI crashes.  How can I recompile and work with it on my CVI 2009 computer?

 

Am i missing something here?  Tehre are no error messages or warnings or crash reports, CVI just acts like I hit Alt+F4

0 Kudos
Message 1 of 18
(4,039 Views)

Hello -

 

This certainly isn't expected. Is there any way you can post the project to our ftp site ( ftp://ftp.ni.com/incoming ), so that I can try to reproduce the issue here?  Without being able to reproduce the issue, it's going to be difficult to debug.

 

NickB

National Instruments

0 Kudos
Message 2 of 18
(4,038 Views)

Uploaded as TestCVI2009Crash.zip

 

 

0 Kudos
Message 3 of 18
(4,026 Views)

I gave this a try this morning, but I wasn't able to reproduce the crash you were seeing.  However, I didn't have access to PowerSupplies.fp - is there a chance you could add it and it's accompanying files to the ftp site as well?? Just curious, what version of NI-VISA is installed on your computer??

 

Thanks -

 

NickB

National Instruments

0 Kudos
Message 4 of 18
(4,003 Views)

I re-uploaded the zip with PowerSupplies included.

 

I did update the CPU that has CVI 2009 with the latest Device Driver DVD Nov. 2010.

 

NI-VISA 5.0.3

NI-VISA Runtime 5.0.3

IVI Compliance 4.2

MAX 4.7.4

CVI 2009 (9.1.0) (runtime of 9.1.0.428)

 

I am able to recompile and load in 'release' mode.  I just cannot run in debug mode without it silently crashing.

0 Kudos
Message 5 of 18
(3,993 Views)

I've tried again, but I'm still unable to reproduce the crash you're seeing.  Let's try a different approach.

 

I've created a new version of the CVI environment DLL, and this time when building goes badly, you should get a Windows crash dialog.  You can download this debug version of the environment dll at ftp://ftp.ni.com/outgoing/CVICrash/

 

Please rename the current cvi.dll in your program files\national instruments\cvi2009 folder and place this new dll in its place.  Then follow the steps outlined here to generate a crash dump when you try to do a debug build.  If you can then post the crash dump back up to the ftp site ( ftp://ftp.ni.com/incoming ), I'll take a look right away.

 

When you're done getting the crash dump, remember to restore your official release version of the dll.

 

Thanks -

 

NickB

National Instruments

0 Kudos
Message 6 of 18
(3,983 Views)

Uploaded the crash report as CVI crash report.txt

 

Thanks

0 Kudos
Message 7 of 18
(3,943 Views)

Thanks ngay -

 

Actually - could you please post the .dmp file that is created?? Sorry I wasn't more specific about this in my last post.

 

Thanks -


NickB

National Instruments

0 Kudos
Message 8 of 18
(3,940 Views)

HMM so I'm using WinDbg, where is the dump file created?

 

I'm looking around but can't find it.  The WinDbg program pops up with an internal window of what I copied to you.

0 Kudos
Message 9 of 18
(3,936 Views)

Ah I figured out the .dump [filename] and .dump /ma [filename] commands.  Transferring now as cvi crash.dmp and cvi crash large.dmp

0 Kudos
Message 10 of 18
(3,932 Views)