what gdb version do you use? any issues?!

[adfm]

Hello all

I've been having some issues with gdb and I decided to downgrade to gdb 6.6.

With gdb 7.0, and while debuguing, CB would often crash if I had anything of the STL on the watch list. Better yet, gdb would crash and CB would go along for the ride.

Another thing that happened and I couldn't figure out why is that sometimes the debuger simply wouldn't start and my application. Instead it would just return to the default CB workspace....

Another issue that I've found in all of the versions of gdb that I've tried is that when I change the debug points while doing debug, they often don't get recognized and the debuger simply skips them as if they aren't there.

I though that these issues were due to some gdb bugs, but now I'm not so sure.

Has anyone had any issues with gbd on CB?

OS: XP SP3
GDB 6.6
GCC 3.4.5 mingw-vista special (hummmm...)

Cheers

[oBFusCATed]

What is your C::B version?
If you're using 8.02, can you try a nightly build and tell us which of the problems are still there.

[adfm]

sh... I forgot to mention the CB version

I'm using the latest build, but this problem has been occurring for quite a while now. I've been doing all of the nightly build updates so...

Cheers

[oBFusCATed]

Another thing that happened and I couldn't figure out why is that sometimes the debuger simply wouldn't start and my application. Instead it would just return to the default CB workspace....

I have the same problem, for a console project the terminal is started but the debugged program is not, and there is no pattern at all.

Another issue that I've found in all of the versions of gdb that I've tried is that when I change the debug points while doing debug, they often don't get recognized and the debuger simply skips them as if they aren't there.

This should not happen, can you provide simple project + steps to reproduce?

I'm on linux 64bit gdb 7.0.x ... debugger branch

[adfm]

I have to try with a simple project.

I actually only work with CB on a huge project and I don't know if that can be an issue when debugging...

[TerryP]

I very rarely need to use a debugger, when I do, it's usually the one supplied by my OS. That usually varies between GDB 5.x and 6.x. This workstations got GCC 4.2.1 / GDB 6.1.1 but I've yet to use C::B for debugging.

[adfm]

I just got a new PC and I installed Kaspersky  AV on it. I noticed that when I tried to debug a test project for the first time the AV popped up and showed me a message about "gdb is trying to inject into another program. bla, bla, bla" and terminated gdb

the output pane on CB read this:
Debugger finished with status 1

This is just about what happened to me before... I have no idea if it was due to that, but... just some extra input|

[MortenMacFly]

the AV popped up and showed me a message about "gdb is trying to inject into another program. bla, bla, bla"

What a bad AV solution. I would not trust such an AV software. Who on earth knows what else is being blocked...?!

[autobot]

Kaspersky is not that great, but when injection is occuring it is nice to be notified at least once so you can decide if this is a 'trusted' application.