   GDB and constructors
  I have been trying several times to set a breakpoint in a constructor with GDB, but it has not worked, even though I have upgraded to the latest version. A google groups search landed me this little piece of information:quote:When gcc 3.x compiles a C++ constructor or C++ destructor, it generates2 or 3 different versions of the object code.  These versions haveunique mangled names (they have to, in order for linking to work), butthey have identical source code names, which leads to a great deal ofconfusion.  Specifically, if you set a breakpoint in a constructor or adestructor, gdb will put a breakpoint in one of the versions, but yourprogram may execute the other version.  This makes it impossible to setbreakpoints reliably in constructors or destructors.gcc 3.x generates these multiple object code functions in order toimplement virtual base classes.  gcc 2.x generated just one object codefunction with a hidden parameter, but gcc 3.x conforms to a multi-vendorABI for C++ which requires multiple object code functions.Are there any workarounds for this? 
  Take this with a grain of salt since I haven''t used gdb since man first tamed lightning and set it to work compiling C programs, but did you try putting a call to a dummy function in the constructor and then setting a breakpoint inside the dummy function? ;  Well the thought did occur to me, but it''s not really what I want. I''m not asking this because of a specific problem I have, but because I could have used a breakpoint in constructors many times lately and it''s annoying to have to insert lots of cout statements instead because the debugger doesn''t work.Oh well, I hope they fix it in the next version! 