Re: vector::operator[]

[Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>]

On Tue, 2005-11-29 at 12:03 -0600, Benjamin Kosnik wrote:
> > What would be even better (but this is a total dream for the time being
> > I think) would be to have some king of debug classes. The idea would be
> > to tag the debug information with some grouping information (eg
> > Standard_C++_Lib, MyLibDebug, ....) and to allow the user to select the
> > debug classes he want to use from the debugger...
> 
> Indeed, this would be cool.
> 
> There was some talk of integrating this kind of thing directly into the
> debugger when the frysk project was getting started.
> 
> http://sourceware.org/frysk/
> 

Thank's for the tip, I will monitor frysk to see what I can do with it.

> > But maybe this is not totally a dream (at least for some uses), if we
> > tie the debug classes to namespaces then the debugger could use the
> > mangled names to automatically disable the stepping into std methods and
> > functions, etc... I do not like the idea of tying debug classes to
> > namespaces, but this could be an easy first step strictly located into
> > gdb...
> > 
> > Is this feasible at all ???
> 
> I don't believe this is feasible with current gdb, at least in a
> dynamic way, as gdb has enough problems just looking up the correct
> fully-qualified item, without having users request alternates.
> 
> For static compilation units, things like debug mode would work. If you
> want to do something similar with your code, you could use the same
> approach as debug mode.

Thank's, indeed as noted by Jon, the user can achieve part of this (but
quite painfully). I do know that this is not the proper mailing list,
but it seems to me that debugging is more and more a painful experience
with C++. More and more I find myself in the situation of adding
printouts in the code instead of firing up the debugger (well to tell
the truth I fire the debugger, lose half an hour to try make it stop at
the proper place avoiding to go inside all the instanciated templated
methods, and finally I give up and add messages).

Really, I think gcc is a great C++ compiler, the problem nowadays is
more with the debugging experience than with bugs in the compiler or in
the library... Unfortunately, I do not know what to do to improve the
situation...