Remote Debugger Cannot Connect

I’m having an issue that I can’t figure out using 32-bit Arm Remote Debugger Desktop. I have previously used this just fine with a Pi. I am now trying to connect using a Beaglebone Black that is running Linux 5.10.131-ti-r49 Debian. I am launching the debugger using root and everything shows up as it should in the console. The files are transferred, extracted, and launched and then nothing. The IDE just hangs launching and I get an error message from the Remote Debugger that says:

Cannot connect to the debugger yadayada

I have opened all the appropriate ports on both sides but just for good measure I have also tried by disabling all protection on both machines. I have verified DNS is working and I can resolve hostnames in both directions.

I am just trying to launch a very simple desktop app for testing at the moment with a button and a textarea so it’s not code related.

I am using 2022 r2 for both the IDE and the Remote Debugger.

Here’s a little bit of the stubborn stub with IPs and file paths removed.

09:06:11 PM: Connection established
09:06:11 PM: Stub<-IDE    HELLO, 22.2.0a0, Protocol: 6, Local IP: 
09:06:11 PM: Using protocol version 6
09:06:11 PM: IDE Version supported
09:06:11 PM: Stub->IDE    OLLEH, 1.9.039, 6, Remote Address: 
09:06:11 PM: Stub<-IDE    PLATFORM-REQUEST
09:06:11 PM: Stub->IDE    PLATFORM-RESPONSE, Linux, ARM, ELF, Linux 5.10.131-ti-r49 Debian GNU/Linux 11 \n \l
09:06:15 PM: Stub<-IDE    CREATEFILE, DebugTestApp.tar.gz,  Relative path: True, 
09:06:15 PM: Stub->IDE    CHALLENGE, 
09:06:15 PM: Waiting for RESPONSE
09:06:15 PM: Got a RESPONSE packet, about to decrypt (32 bytes)
09:06:15 PM: Stub<-IDE    RESPONSE, 
09:06:15 PM: Response accepted
09:06:15 PM: Creating file: 
09:06:15 PM: Created the file list
09:06:15 PM: Added the file or folder to the file list
09:06:15 PM: Stub->IDE    FILECREATION, File ID: 0, Status: 0
09:06:15 PM: Stub<-IDE    FILEINFO, File ID: 0, Size: 1.972621e+7, Compressed: False, Stub Delete: False
09:06:16 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:16 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:16 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:17 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:17 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:17 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:18 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:18 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:18 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:18 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:19 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:19 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:19 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:19 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:20 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:20 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:20 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:21 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:21 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:21 PM: Stub<-IDE    FILEPART, File ID: 0
09:06:21 PM: Stub->IDE    FILEWRITTEN, File ID: 0, Status: 0
09:06:21 PM: Stub<-IDE    FILELAUNCH, File ID: 0, Launch in Terminal: False, Command line args: 
09:06:21 PM: Stub->IDE    CHALLENGE, 
09:06:21 PM: Got a RESPONSE packet, about to decrypt (32 bytes)
09:06:21 PM: Stub<-IDE    RESPONSE, 
09:06:21 PM: Response accepted
09:06:21 PM: Decompressing DebugTestApp.tar.gz
09:06:27 PM: Untarring DebugTestApp.tar
09:06:30 PM: Launching DebugTestApp
09:06:30 PM: tar.gz was launched
09:06:30 PM: Stub->IDE    FILELAUNCHED, File ID: 0
09:06:30 PM: Stub<-IDE    SEEYA
09:06:30 PM: Connection closed

Any ideas? Thanks.

If you build that app and copy it to the device, does it launch? I suspect it’s crashing on launch.

Yes I have built the app and ran it successfully it only fails using the debugger.

I have also tried giving the Debug version of the executable chmod +x permission.

So it turned out to be an AVAST antivirus issue on the computer running the IDE. :roll_eyes:

It works fine with Avast enabled using the remote debugger on a Windows OS, it only blocks connections from Linux for some reason.

2 Likes