Remote Session Shows No Errors When Running LabVIEW Broken Executable

Updated Jul 19, 2024

Reported In

Software

  • LabVIEW

Issue Details

  • When trying to run a broken LabVIEW executable (with a broken arrow) from a remote debugging session I get no errors, when doing the same procedure locally the broken arrow pops up a window showing an error message. Why is the same behavior not happening from the remote debugging session?

Solution

This behavior is expected and happens due to a LabVIEW limitation.

The way remote debugging works is by loading the source VI on the debugger side that match the VIs on the execution side and syncing execution info between them. Since the execution side may be a different platform than the debugger side, the debugger side can't be used to determine errors and LabVIEW does not have a way to sync errors from execution to debugger. End result is that the debugger doesn't know what the errors are on the execution side. It only knows that the VI is broken.

 

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.