I've had a look into the Documentation and Examples (`http://83.212.101.132/`) but I can't find anything.

Is it even possible?

In large scale projects, like the one I'm working on right now, I most definitely prefer to use OOP. And not being able to support it would be a big letdown.
['https://Stackoverflow.com/questions/26009586', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/4037009/']
Remote debugging of embedded systems:
GDB, as a server, must be compiled into the debugging target build in order to support connected GDB clients. When running on the client side, there must exist a copy of the target source as well as an unstripped (of symbols) version of the executable.

GCC compilation should be done with the -g flag.

On the target/server side, run with

```
gdbserver <port> --attach <pid> or gdbserver host:<port> <program>

```

On the client side, run gdb and then

```
(gdb) target remote IP:PORT

```

What gdb client to run? Must be built with the right target processor in mind, for example

```
.../toolchain/bin/powerpc-linux-gdb core/mydaemon/src/mydaemon -x gdb-command-script

```

-x is a filename option

Hope this helps!
Remote debugging of embedded systems: GDB, as a server, must be compiled into the debugging target build in order to support connected GDB clients. When running on the client side, there must exist a copy of the target source as well as an unstripped (of symbols) version of the executable.

GCC compilation should be done with the -g flag.

On the target/server side, run with

gdbserver --attach or gdbserver host: 
On the client side, run gdb and then

(gdb) target remote IP:PORT
What gdb client to run? Must be built with the right target processor in mind, for example

.../toolchain/bin/powerpc-linux-gdb core/mydaemon/src/mydaemon -x gdb-command-script
-x is a filename option

Hope this helps!