This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: (Not) debugging STL


> I don't know.  Maybe not, if someone came up with a good user
> interface for it.  I recommend searching the list archives for more; I
> think it was discussed within the past six months sometime.

What I would suggest is a command say 'skip arg' or 'trust arg', where
arg is either a
      * file name (e.g. nobug.h)
      * a prefix (e.g. /usr/include or /usr/include/*)
Or even more:
      * a function
      * a class
      * a range of lines

> > Do gdb have some scripting language? If yes, would it be possible to
> > implement a macro that simply iterates 'step' while we are in a file
> > under /usr directory?
> 
> GDB's current scripting language is not good enough for this.  I hope
> to add a more powerful one this year.

Then, my next idea is to use the gdb interface of emacs. It should be
trivial to do a lisp function doing this, but I couldn't figure out how
to do that. For example how to obtain the file name of the currently
debugged line in emacs/gud/gdb?

Best regards,
Alpar



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]