I am confused for debug in the codeblocks

[mmkider]

in winxp with mingw 3.4.5
Using gdb 6.6, I can debug codeblocks source, but I can't debug wxwidget sample code.

I change gdb 6.6 into gdb 6.83, and then I can debug wxwidgets sample code but can't debgu codeblocks source .

How do I choose?

[mmkider]

In these days, I am sure this problem is gdb problem.

Now I downgrade gdb into 6.3.2 and debug codeblocks source is good.


I am sorry I have misunderstood.

[MortenMacFly]

Now I downgrade gdb into 6.3.2 and debug codeblocks source is good.

Yes - that's some weirdness I had to learn, too.

[thomas]

Funnily, gdb 6.8 works without problems.

[mandrav]

Funnily, gdb 6.8 works without problems.

Depends on how you define "problems" .
For example, with gdb 6.8 on windows, if I enable the "catch C++ exceptions" option it causes an internal gdb error...

[thomas]

Again... funny. Because this is probably the best feature you've ever added, I have it enabled of course, and it works just fine.
Well, for me, anyway.

[MortenMacFly]

Well, for me, anyway.

Not for me, too (on Windows). :-(

[MortenMacFly]

Funnily, gdb 6.8 works without problems.

Lucky bastard! :lol:

[thomas]

Maybe you're all using the SJLJ exception variety of the compiler? Dunno, but... since my gdb executable should be the same and do the same as yours, that's the only thing I could imagine why it should work for me and not for you.

[mandrav]

...why it should work for me and not for you.

I believe it may have to do with the compiler one uses. I, for instance, use the old 3.4.5. I know... maybe I should consider finally moving on .

[MortenMacFly]

I, for instance, use the old 3.4.5. I know...

Me Myself and I uses this version, too.

maybe I should consider finally moving on .

...me probably not... or should I...?!

[thomas]

You definitively should.

I'm using the 4.2.1-DW2 as main compiler for many months, which really works nicely. Heh, I'm the first person to start puking if something doesn't work 100% well.
There's never a problem with gcc 4.2, except for a single case where I saw it issue a wrong warning about a presumably uninitialised variable after turning on "all" warnings plus "extra" warnings.

For playing around, I'm using TDragon's 4.3 build which mostly works ok too, apart from occasional failures (have seen an internal compiler error once, and have seen incorrectly optimised code on two occasions) which kind of limit its production use. The gcc 4.3 branch sadly still needs a bit of work.

[killerbot]

on windows I have been using 4.2.1 dw2 for many months now (maybe already a year or longer,can't remember). No issues thus far.