Code::Blocks Forums
User forums => Embedded development => Topic started by: Typz on May 07, 2008, 09:27:48 pm
-
Hello,
For embedded development, at work, we need to use custom commands to control GDB.
Thus, we implemented patches to let us configure this. I just posted the patch on BerliOS (patch #2458: "Custom GDB commands (run, continue...) for remote debugging").
With this patch, the GDB commands to use can be customized for each build target, in the remote gdb configuration (there is a new tab). Please note however that this configuration applies even if remote debugging is not enabled for the target.
The commands which are customized are: run, continue, quit, get thread list (info threads), switch thread (thread %i).
If a field is left empty, the default command is used.
Can somebody please check the patch and commit ?
Thanks,
-
Can somebody please check the patch and commit ?
Very interesting! I hope/guess Yiannis (mandrav) will note that one too and respond. He is into such things, too ATM (IMHO).
-
Can someone upload a windows build with this patch please?
-
Can someone upload a windows build with this patch please?
Just wait for the next nightly...
-
I can't figure out where the settings are for this in the newest nightly (May 19)?
-
patch 002458 Custom GDB commands (run, continue...) for remote debugging : this has not been applied (yet??) !!
-
Need this patch very urgently!
When I first hit the run button I can see the gdb error in the
gdb debugger console 'target does not support run',
On second hit the button emits continue.!?
I need continue from the first!
The stop button also doesn't seem to work as expected.
I need a break command there but I tries to end the session?
I know there was a keyboard shortcut (F8?) for this but ....
Apart from that C::B looks like a good IDE for embedded development.
Greets,
Joerg