I Can't Step Into a LabWindows™/CVI™ DLL When Calling From TestStand

Updated Aug 14, 2018

Reported In

Software

  • LabWindows/CVI

Issue Details

I have a DLL that I created in LabWindows/CVI and I am calling into this DLL from NI TestStand. When I use a breakpoint to halt execution in LabWindows/CVI, I expect to be able to Step Into my DLL, however the Step Into button seems to exhibit the same functionality as Step Over. How can I correct this behavior?

Solution

To enable the Step Into debugging options in a LabWindows/CVI DLL called from TestStand, it is necessary to ensure that your LabWindows/CVI adapter in TestStand is set to execute steps in an external instance of LabWindows/CVI, rather than in the runtime engine.



This setting can be adjusted in:

TestStand >> Configure >> Adapters >> (radio button) LabWindows/CVI >> Configure >> Step Execution

When a breakpoint is set on the DLL, the LabWindows/CVI environment will be entered, allowing you to step into your DLL. 

 

Additional Information

In this case, it is also worth confirming that the Configuration is set to "Debug" in:

LabWindows/CVI>>Options>>Build Options>>Configuration Options

Before compiling the DLL or EXE you intend to debug.

WAS THIS ARTICLE HELPFUL?

Not Helpful