LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Are CDB files generated for the trial version of LabWindows/CVI?

I'm trying to figure out why I can't see the generated cdb files, since everywhere I look, it says you should be able to do that if you configure your build as a debug build. Is this something that you just can't see if you're using the free trial version or??? I know they exist somewhere because the IDE can properly debug the application.

0 Kudos
Message 1 of 5
(80 Views)

Hi cbwolfe,

 

Trial version should not make such a difference.

You might have set the location for the output EXE different than the project folder (see target settings).

CDB file is probably resides in the original project folder together with the source files.

 

Can you open an NI example and try the same?

(also make sure system and hidden files are visible, just be safe)

Hope this helps,

S. Eren BALCI
IMESTEK
0 Kudos
Message 2 of 5
(50 Views)

.cdb files are not generated for recent versions of CVI (I seem to remember starting from CVI2015)

Which version are you using?



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 3 of 5
(43 Views)

LabWindows/CVI 2020

0 Kudos
Message 4 of 5
(28 Views)

For some background, my job title is Embedded Software Engineer. I am helping one of our junior test engineers get his development environment set up since I'm one of the few(2) in the building that has any LabVIEW experience. My goal was to move away from the IDE all together and use something like VS Code or Visual Studio since that's what we use here. Everything seems to work in VS Code and Visual Studio except for debugging. Since it doesn't have any of the debugging symbols, gdb doesn't know how to parse the executable. Normally, when we write code for embedded, there are files that are generated with the appropriate symbols for the debugger to look at(elf files). Like, I know for a fact that some sort of debug symbol file exists SOMEWHERE since the built in debugger in the IDE uses it. I haven't gone through the process of doing what we do for our embedded projects(CMake -> Make and Ninja -> gcc/clang) since that is somewhat of an involved process. 
And the hidden files are visible. That's something that I thought about too. 

0 Kudos
Message 5 of 5
(27 Views)