debugging on linux: strange symbols, files open twice, "nothing to be done"

[mandrav]

Right, this seems to be some kind of gcc/gdb bug.
This bug can be circumvented by removing the "virtual" keyword from the TestDebugger class' ancestors list

Code Select Expand

class TestDebugger : public foo::Base1 ,public Base2

[CuteAlien]

Right, this seems to be some kind of gcc/gdb bug.
This bug can be circumvented by removing the "virtual" keyword from the TestDebugger class' ancestors list

Code Select Expand

class TestDebugger : public foo::Base1 ,public Base2

That would work in my reduced test-case... but the real classes are derived from a class doing the reference-counting so that would introduce diamond inheritance problems :-(

Edit: I'll report it to the gdb people.

[Jenna]

Have you tried to use a pointer ?

Code Select Expand

TestDebugger* iAmTheBug;

That works for me in the test-case.

[CuteAlien]

Have you tried to use a pointer ?

Thanks, nice workaround :-) That way I can actually debug it.

[mandrav]

... but the real classes are derived from a class doing the reference-counting so that would introduce diamond inheritance problems :-(

(emphasis added)

Which is why you shouldn't create such objects on the stack but only on the heap...
So, Jens is right (again) :

Have you tried to use a pointer ?

[CuteAlien]

Which is why you shouldn't create such objects on the stack but only on the heap...
So, Jens is right (again) :

Yeah, yeah, but sometimes you want to use classes in different contexts and except for debugging that would have worked. In that case it was a context specifically created for debugging, so every class needed was just in the function *sigh*.

Anyway, I could debug now, but while doing that I found out that I was too early when I announced that the problem with the strange symbols that get inserted sometimes in the sourcecode (mentioned at the start of thread) has been fixed with the newer nightly build I'm using. It certainly got a lot better, but I think it's somehow related to the speed of the debugger. When I stepped deeper and deeper into a library the stepping started to take more and  more time. And as soon as that happened I got the strange characters back when I pressed on stepping before the debugger was finished with it's current step. So that might also be something worth looking into.