User forums > Embedded development

Codeblocks, gdbserver and beagleboard

(1/2) > >>

doragasu:
Hi all!

I've been using codeblocks for some months, developing x86 Linux applications, and it's a great app. Now I have to debug applications for a beagleboard running Angstrom Linux distribution (ARM Cortex A8). I have gdbserver running in the beagleboard, and I could connect and debug applications using arm-angstrom-linux-gnueabi-gdb (the cross debugger), connecting it to the gdbserver in the beagleboard.

The problem is when I try to debug with codeblocks. I have configured gdb with the ip/port of the Beagleboard, and with some custom commands. When I launch the debugger in Codeblocks, it connects with gdbserver in the beagleboard, but the application starts, and finish without hitting the the breakpoints.

I suspect the error may be due to Codeblocks calling gdb instead of arm-angstrom-linux-gnueabi-gdb. How can I make C::B call arm-angstrom-linux-gnueabi-gdb instead of gdb?

Any suggestions are greatly appreciated.

Thanks for reading.

MortenMacFly:

--- Quote from: doragasu on April 23, 2009, 01:50:22 pm ---I suspect the error may be due to Codeblocks calling gdb instead of arm-angstrom-linux-gnueabi-gdb. How can I make C::B call arm-angstrom-linux-gnueabi-gdb instead of gdb?

--- End quote ---
Did you try setting the name of the debugger's executable in the compiler settings -> toolchain options?

doragasu:
I couldn't have a look to this until today. I didn't notice you can configure the different toolchains under 'Settings/Compiler and debugger...'. I was compiling my project using a custom makefile. I'll try to configure the toolchain in C::B and if it works, then I will try also to use the debugger.

Thanks a lot MortenMacFly!

doragasu:
Finally I got it to work. Using Morten suggestions, I can build the project and remote-debug it with C::B interface.

Only one thing lasts to reach the perfect-remote-debugging-experience. I have to manually copy the generated executable to the beagleboard (I use scp for this) and manually launch gdbserver in the beagleboard (I use ssh for this). Can these two steps also be automated? It would be great if each time I hit F8 for debugging, the generated binary was transferred to the beagleboard and gdbserver was launched before starting the debug session. I think it can be done each time I build the file, but can be done each time I start the debug session?

dje:
Hi !

Did you try the post build steps ?

Dje

Navigation

[0] Message Index

[#] Next page