Debugging Executables
Appearance
Executables created in LabVIEW can be debugged after having been compiled into an executable, (*.exe). However, this is only able to be done if "Enable debugging" was enabled in the build specification when the application was compiled.
Build Specification Settings
Under the "Advanced" category in the Build Specification:
- Enable debugging
- Enabled - "Builds in" the ability to connect to and debug the built application. This ability can then be enabled/disabled by setting the appropriate key in the [AppName].ini file after it has been compiled.
- Disabled - Completely disables any ability to connect to and debug the application once built. This ability can not be enabled even if the appropriate keys have been added and set in the [AppName].ini file.
- Wait for debugger on launch
- Enabled - If "Enable debugging" has been set, this setting allows the built application to be launched and accessed, but the application does not automatically run. The run arrow will have to be clicked to start running the application.
- Disabled - The application will begin running immediately when the application is launched.
Debugging an Executable
In order to debug an executable that has been compiled with the proper settings (see above), the application must already be launched either on the local computer or on a computer accessible via a network connection.
- In LabVIEW, select the Operate >> Debug Application or Shared Library...
- Enter the machine name or IP address of the computer that is running the application. If the application is running on the local machine, enter localhost.
- If "Application or shared library" drop-down doesn't show the name of the application that you are looking for and the application has been configured properly, click on "Refresh".
- Select the application that you wish to debug and click on "Connect".
At this point, the application should "download" and you should be able to use the LabVIEW debugging tools in the application.