Has anyone ever experienced an issue where the remote debug fails with the error "failed to connect to the application"? I am working on an existing project which is a few years old. Up until now it included the compiled code with source. This project is now being managed under source code control so I went through the project and marked all project VIs to separate compiled code from source. I had no issue doing this. The application ran fine in the development environment and was built as an exe without any issues. The executable ran just fine but when we went to investigate a bug we could not connect with the remote debugger. Going into the project and unmarking "separate compiled from source" and rebuilding allows us to connect the remote debugger. I tried the usual with cleaning the compile cache and doing a clean before the build. None of this seemed to make a difference. I have many other projects which have the compiled code separated which we can use the remote debugger to debug the executable. Any thoughts on what the issue might be?

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

LV 2015, Remote Debugging and Separate Compiled From Source Issue

Have you tried compiling this on a different system with a fresh LabVIEW installation? Maybe the corruption is coming from within compiler.

Casey G.

Message 11 of 12

(481 Views)

Author

I haven't tried it with a fresh install but I have tried it on two different machines. Same result.

Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Message 12 of 12

(468 Views)

LabVIEW

LV 2015, Remote Debugging and Separate Compiled From Source Issue

Re: LV 2015, Remote Debugging and Separate Compiled From Source Issue

Re: LV 2015, Remote Debugging and Separate Compiled From Source Issue