07-15-2025 01:58 AM
Hi everyone,
I am desperately trying to remotely debug a LabVIEW-built standalone application running on a RHEL 9.4 Linux target machine.
What I did:
- Enable Debugging in build parameters
- Copied the EXE to the target machine
- Installed the correct LabVIEW Runtime Engine
- Made sure to tun the exe on the target manually
On the target machine I disabled:
- firewalld
- iptables
- SELinux
- Verified no local firewall is blocking TCP port 3580
- The port does not show up in 'ss -lntp' after launching the exe
Run strace and saw that the EXE is trying to connect to 127.0.0.1:3580, but receives a ECONNRESUFED
Problem:
When I run my standalone application, I get a pop-up window which says, "Failed to start debug server"
Questions:
Am I operating this even right? Should the LAbVIEW-built EXE listen on port 3580 as a server, or does it act as a client?
Because I would guess that the "Debug Server" would be embedded to the application and when I run it, it wait for a connection from my
developement machine where I have the LabVIEW Pro with the debugging tools? Or do I need to have the LabVIEW IDE installed on the target machine aswell? (But then why remote debugging).
Unfortunately the internet and documentation of NI doesn't really give hints to this error.
Any tips, clarification or documentation links would be highly appreciated. I've read that port3580 needs to be open, but so far the EXE doesn't seem to bind to it.
Thanks in advance.
Musa
Let me know if you'd like to tweak the tone or include more technical detail (e.g., the strace output)
08-05-2025 02:39 AM
I fixed this issue by copying the program nisvcloc under /usr/sbin/ to my target machine under the same path and ran it with:
root@target_machine: /usr/bin/nisvcloc -D
This program now LISTENS on port 3580 and waits for a connection from the LabVIEW Debugging tool.
It's strange that this usecase is not documented.