How do I debug LabWindows/CVI code from TestStand?
Debugging LabWindows/CVI code modules is allowed for steps that use the C/CVI Standard Prototype Adapter. The code modules can be either source code or DLLs with the debugging option enabled. To debug LabWindows/CVI code, you must first configure the LabWindows/CVI Standard Prototype Adapter to execute the code module in an external LabWindows/CVI process. In the Sequence Editor, select Configure » Adapters » C/CVI Standard Prototype. Now, if you stop at a breakpoint in your sequence, you can Step Into the LabWindows/CVI code module. Consult Chapter 6 of the Getting Started manual for more information on debugging test code. If you use the DLL Flexible Adapter, TestStand will not be able to launch the LabWindows/CVI debugger. Instead, you can use the DLL debugging tools built into LabWindows/CVI 5.0. You will have to launch TestStand from LabWindows/CVI as an external process. For more information on debugging an external process within LabWindows/CVI, consult Chapter 4 of the LabWindo
Related Questions
- I try to debug the VHDL code in problem 1, but I keep getting "ieee_std_logic_1164.ALL not found" error. What could be wrong?
- I try to debug the VHDL code in problem 1, but I keep getting "ieee_std_logic_1164.ALL not found" error. What could be wrong?
- How do I debug my LabWindows/CVI application once I have compiled and built it on Linux?
- How do I debug my LabWindows/CVI application once I have compiled and built it on Linux?
- How do I debug LabWindows/CVI code from TestStand?
- How does patching object code affect debug?
