Debugging an Executable on a Real-Time Target That is Not a Start-Up Executable

Updated Mar 15, 2018

Reported In


  • LabVIEW
  • LabVIEW Real-Time Module



Issue Details

I have created and deployed an executable to my real-time (RT) target. When I set this executable to Run As Startup, then try to debug it remotely by selecting Operate->Debug Application or Shared Library while the executable is running, everything works fine.

However, if I try to debug an executable that was started through VI Server rather than setting it as a startup EXE, I get a message that says No debuggable applications or runtime libraries found. Why is this the case?

Figure 1. No debuggable applications or runtime libraries found


In order to debug an executable running on an RT target, it has to be a startup executable. 

If you start the executable using VI Server or interactive mode (clicking the run button in the LabVIEW project), this downloads a compiled version of your code to the target without the debugging feature which allows remote debugging. For this reason, you will have to explicitly make the executable a startup executable in order to be able to debug it remotely while it is running on your controller.

Additional Information