-bash: ./RemoteDebuggerConsole: cannot execute: required file not found

Targets Raspberry Pi
1

I’m stumped… Today I’ve been setting up a Raspberry Pi 4 with the latest Bookworm Lite OS and I tried to run a Xojo console app that I wrote but it fails to launch. So, I decided to copy the RemoteDebuggerConsole software over to the Pi and found that I couldn’t launch the debugger either. I get the following message:

-bash: ./RemoteDebuggerConsole: cannot execute: required file not found

I am executing the debugger as root so privileges shouldn’t be an issue. And all the debugger files have been set to executable:

root@web-server:~/RemoteDebuggerConsole# ls -al
total 1696
drwxr-xr-x 4 root root    4096 Feb 25 19:09  .
drwx------ 8 root root    4096 Feb 25 19:09  ..
-rwxr-xr-x 1 root root 1716268 Feb 25 19:09  RemoteDebuggerConsole
drwxr-xr-x 2 root root    4096 Feb 25 19:09 'RemoteDebuggerConsole Libs'
drwxr-xr-x 3 root root    4096 Feb 25 19:09 'RemoteDebuggerConsole Resources'

This is the first time I’ve attempted to employ a Raspberry Pi greater than version 3 and an OS greater than Buster.

Can anyone help me with this?
-Wes

PS. I tried a second Xojo console app and it fails to execute also. Everything was working fine on my Raspberry Pi 3’s with Buster. :frowning:

2

Use ldd to check for missing libraries. I have no problems with remote debugger on Pi, but Lifeboat installs a bunch of stuff for me.

3

Yeah, I tried that and this is what it reported:

root@web-server:~/RemoteDebuggerConsole# ldd ./RemoteDebuggerConsole
	not a dynamic executable

I don’t know what to do with that…

4

Do you have the right architecture? file should help us determine that.

There were certain Xojo versions where the 32 bit debugger was labeled 64 bit. I don’t recall what versions that occurs in.

5

Thanks for the help Tim. You made me question if I installed the correct OS. I finally gave up and re-imaged the Raspberry Pi with Bookworm 32bit Lite. Everything worked! I can only assume that I grabbed the wrong Raspberry Pi OS image (probably Bookworm 64bit Lite) and that caused my issues. Anyway, all is well now! Thanks again.

6

To be clear, the 32bit OS is the one that’s the “wrong OS” for a Raspberry Pi 4.

That this solution worked means to me that you were using a release of Xojo where the debugger was mislabeled.

Personally, I would reimage the Pi using the modern, 64bit OS and grab a correctly labeled 64 bit remote debugger stub from an older release. I made a ticket about this situation if you would like specifics and details for which version to grab.

7

Update: Now that I’m at my desk, I’ve found the ticket. #76743 - Remote Debugger Console Linux ARM 64-bit is 32-bit.

1 Like
8

I’m not sure I understand:

“To be clear, the 32bit OS is the one that’s the “wrong OS” for a Raspberry Pi 4.”

My Pi 4 only has 2 Gigs of memory so that makes it a good candidate for the 32bit OS. Even a Pi 4 with 4 Gigs doesn’t really need the 64bit OS. My understanding is that the 64bit OS is primarily for Pi’s with more than 4Gigs of memory. What am I missing?

9

But my issue extended beyond just executing the Xojo Remote Debugger. I was unable to execute two of my own console applications which has no relation to the Xojo debugger. Now that I’m running the 32bit OS my console applications and the debugger seem to be executing properly.

Btw, I’m running Xojo 2024 r4.2 which I believe has the debugger issue corrected.