C::B debug (gdb) with breakpoints pending is VERY SLOW ...

[oBFusCATed]

1. No way breakpoints to be saved in the cbp file, for the other option, there is a missing API, which I need to implement to be able to implement this feature
2. I can (and will) provide scripting support for setting breakpoints. Another thing I think will be useful will be the addition of "enable all, disable all" feature. I think, I can provide this, too.

Stay tuned...

[kccheng]

1. No way breakpoints to be saved in the cbp file, for the other option, there is a missing API, which I need to implement to be able to implement this feature
2. I can (and will) provide scripting support for setting breakpoints. Another thing I think will be useful will be the addition of "enable all, disable all" feature. I think, I can provide this, too.

Stay tuned...

That will be great.  And I can help to test your code, that's at least I can do right now :-)

Regards
KC

[TedK]

I have been using Code::Blocks 13.12 for several months on Kubuntu (14.10 and 15.04), and debugging a C++ application has been painful. Stepping through a single line of code can take between 10 s and 5 min. Initially, I had GDB 7.8 and then upgraded it to 7.9 but this did not solve the problem. And it looks like the problem is not in GDB because I can debug with GDB in command mode without any delays. I tried to find a solution, but it looks like there is no one. Some people were blaming libc6-dbg, but I have the latest one. I suspect that CB debugger plugin is at fault and it looks like no one is willing to fix it. So I will probably be switching to Eclipse or CodeLite.

[oBFusCATed]

If you have too many watches added to the watches window then this will slow stepping down.
On newer versions there is an option to disable the automatic update of watches, which can speed things a bit.

This problem is unfixable in the current code, so you'll have to wait for the gdb/mi plugin.