CLion: Run/Debug Configurations: What is the difference between Remote GDB Server and Embedded GDB Server?

Answered

I'm doing an embedded project so in Run/Debug Configurations I selected create Embedded GDB server configuration.   That does not provide anything for SSH credentials etc.  And seems to serve no purpose, and definitely won't connect to gdbserver.

On the other hand when I realized the Remote GDB Server configuration existed it all just worked perfectly on my embedded target. 

Just curious what the intended difference of these two are. 

5 comments
Comment actions Permalink

Hello!

The Embedded GDB Server configuration is intended for debugging on-chip with GDB server - https://www.jetbrains.com/help/clion/embedded-gdb-server.html.

The Remote GDB Server configuration is intended for debugging on the remote machine - https://www.jetbrains.com/help/clion/remote-gdb-server.html.

0
Comment actions Permalink

haha, too funny.  The one that works for on-chip debugging for me with gdb server is the Remote GDB server configuration.

The Embedded version provides no means to set ssh credentials to talk to the gdbserver on my ARM target.

Remote GDB server configuration for an embedded ARM does work incredibly well TBH, but seemed like I might be not understanding something.  I suspect I'm still missing something basic.

Yes I did check that the executable was actually being downloaded to the target and that it was running there during debug.

0
Comment actions Permalink

The Embedded GDB Server configuration: the GDB server is installed on the same machine where CLion is installed.

The Remote GDB Server configuration: the GDB server is installed on the remote machine.

Is it more clear now?

0
Comment actions Permalink

OK, well I guess its a question of semantics.

What I needed was CLion and gdb running on host, and gdbserver (executing my program) on the target. 

It works great so I'm happy.  It's so good I can't even tell the difference between running on the target ARM and my x64 ubuntu machine.

0
Comment actions Permalink

 >What I needed was CLion and gdb running on host, and gdbserver (executing my program) on the target. 

For such scenario the Remote GDB Server configuration is the best choice indeed. I'm glad it suits your needs :)

0

Please sign in to leave a comment.