Remote Debugger Console, how does this work?

Targets Linux
1

Greetings,

I have a remote app which fails and i wanted to know why and where it fails for the code side.

I have 2 setups 1 with Debian 12 x86 64 bit machine and 2 raspberry pi 5 as well with 64 bit.

I put the Remote Debugger Console, setup the instance and wait , i send the code to the console , it gets there , then i see :

06:52:20 PM: Decompressing Debugmmh.tar.gz

06:52:21 PM: Untarring Debugmmh.tar

06:52:21 PM: Launching Debugmmh

and that’s about it, the app does not do anything else while i should have an interactive menu to allow me to do some initial configs and as well run some parameters but here noting.

Can someone provide more details as unforunately on the XOJO docs you don’t have much .

Thanks

2

First of all, the remote debugger console is only useful for console and web apps and was really designed for headless servers that don’t have a screen.

3

so i guess for console apps the only way to doit is building , deploy and handle by our own , sweet.

4

That’s not what I said. If you’re running on a raspberry pi with a GUI, try using the Linux arm desktop stub instead. If you’re only logging in with ssh, the console stub will work just fine.

Out of curiosity, when you ran the console stub the first time, it asked some questions and created a config file next to the stub. If you could post that, maybe that will help.

5

Are there technical reasons why both Desktop and Console cannot be merged?
That would confuse less users and avoid to have to choose.

6

Nobody should want to… One is for desktop apps and one is for command line access. You must use the right tool for the right job.

7

Hi Greg, i just said that is a console app, i use it as a helper command line app, so in this case i need to do some debugging, i did tested the latest console debugger on arm64 and as well on a linux x86 64 bit and got same issue , once i enabled break on exceptions i see the break in the code but i never see update on the terminal, in order for me to advance i need to put some parameters , once those are in place the rest goes on.

my issue is that if i put my app as a service once i use service test stop it kills the app and the app does not do the cleanup procedure and i end up with left open dbs and a lot of mess.

I managed to handle that using an argument and calling that from the service config. but so far it works on x86 but it fails on arm . As for the debugging i give up as it is more trouble than help and i ended up having a logging system that output all the breaking points and i managed to solve a lot but the downside is that it become very verbose and it takes more time to cleanup after but you do what you need to do in order to have things going when tools don’t work

8

Yes. For example, when Linux is installed without a GUI, like for a server, the desktop version of the stub will simply not run at all because the desktop manager and libraries are not even installed. That’s what the console stub is for. That special environment where you have no GUI and only command line access to the machine.

I think the confusion here is you guys are thinking that Desktop Debugger Stub is only for Desktop apps and Console debugger stub is only for console apps, whereas Desktop and Console instead refers to the environment that the stub is running under.

6 Likes