sdt
commented
8 years ago Hi @yba35 - thanks for the kind words!
For some reason, the official Raspberry Pi toolchain that I bundle has two separate directories of cross-compile tools.
In the rpxc docker image, one gets mapped to /rpxc/bin with arm-linux-gnueabihf- prefixes, and the other to /rpxc/arm-bcm2708-linux-gnueabi/bin with no prefixes.
The first one is in the default rpxc path, and has a whole lot more in it than the second, including arm-linux-gnueabihf-gdb.
I've never actually tried remote debugging before today, but it seems to work. I followed these instructions. It may be enough to just specify rpxc arm-linux-gnueabihf-gdb to Eclipse.
Here's what I did to test things:
On the raspberry pi, run gdbserver host:2345 ./hello-world
On the dev box, run rpxc arm-linux-gnueabihf-gdb ./hello-world, and then when inside gdb target remote your-raspberry-pi:2345. You may need to specify the ip address, depending on your local DNS setup. You don't need to use 2345 - pick whatever unused port you like.
Let me know how it goes. I'd be interested to see if it all works with CDT, or if there's any other tweaks required.
Hi ! First, a few words to thank you, it is an impressive and very useful work ! I am a total newbie regarding docker, so I apologize by advance if this question is not pertinent, or if the fix is evident.
I just succeeded in compiling a kind of C++ 'hello world' inside the container using a cmake project. Now I want to use 'rxpc gdb' as a client for my Eclipse CDT environment in order to remotely debug a program which runs on the raspberry target using 'gdbserver'. But it seems that gdb is not present by default in the cross-compilation tool flow. Do you think it could be possible to add it by default ? Or give me an hint to add it by myself ?
Thanks !