You can debug stand-alone applications and shared libraries that you create with the Application Builder.

Note The LabVIEW Professional Development System includes the Application Builder. If you use the LabVIEW Base Development System or Full Development System, you can purchase the Application Builder separately by visiting the National Instruments Web site.

Complete the following instructions to debug a stand-alone application or shared library.

Note When you debug applications and shared libraries, you cannot debug reentrant panels that an Open VI Reference function creates or reentrant panels that are entry points to LabVIEW-built shared libraries. You also cannot debug subVIs within Diagram Disable structures. SubVIs within Diagram Disable structures appear as question marks while you debug an application. However, because code in a Diagram Disable structure does not execute, this does not affect debugging.
  1. Before you build the application or shared library, you must enable debugging in the build specification. For an application, place a checkmark in the Enable debugging checkbox on the Advanced page of the Application Properties dialog box. For a shared library, place a checkmark in the Enable debugging checkbox on the Advanced page of the Shared Library Properties dialog box. Enabling debugging retains the block diagrams of the VIs in the build so you can perform debugging.
  2. Place a checkmark in the Wait for debugger on launch checkbox if you want the application or shared library to wait to run any VIs until you run the debugging tool.
  3. Build the application or shared library.
  4. Run the built application or call the shared library from outside of LabVIEW.
  5. From the Project Explorer window, select Operate»Debug Application or Shared Library to display the Debug Application or Shared Library dialog box. The dialog box displays a list of applications and shared libraries with debugging enabled.
  6. If the application or shared library you want to debug is running on a different computer, enter the computer name in the Machine name or IP address text box. Click the Refresh button to view the list of applications and shared libraries with debugging enabled on the remote computer.
  7. Select the application or shared library you want to debug.
  8. Click the Connect button to perform debugging. LabVIEW downloads the application or shared library and the front panel of the startup VI appears for debugging. If you enabled Wait for debugger on launch, you must click the Run button to start the application or shared library.
  9. Use the block diagram of the startup VI to debug the application or shared library. You can use probes, breakpoints, and other debugging techniques to identify problems. You then can correct any problems found during debugging.
Note If you are debugging using a custom probe that uses a Call Library Function Node on a shared library that was not built with the application or shared library you want to debug, you must place the shared library in the same directory as the application or shared library you want to debug.
  1. After you finish debugging, close the startup VI, which also closes the remotely controlled application or shared library. If you want to disconnect the remotely controlled application or shared library without closing the startup VI, right-click the startup VI and select Remote Debugging»Quit Debug Session from the shortcut menu.

The following scenarios might cause the No debuggable applications or runtime libraries found error to appear.

  • The debuggable application or shared library was not loaded or the debuggable shared library was unloaded by the application.
  • The configuration ini file of the shared library or application, created by the Application Builder, was not distributed with the shared library or application.

Building and Distributing Applications Home