Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Alpár Jüttner" <alpar@cs.elte.hu>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: (Not) debugging STL
Date: Sat, 03 Mar 2007 10:46:00 -0000	[thread overview]
Message-ID: <1172864572.4272.21.camel@mikro.mikro> (raw)
In-Reply-To: <20070301124621.GA11292@caradoc.them.org>

> 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



  reply	other threads:[~2007-03-03 10:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 12:05 Alpár Jüttner
2007-03-01 12:19 ` Daniel Jacobowitz
2007-03-01 12:40   ` Alpár Jüttner
2007-03-01 12:46     ` Daniel Jacobowitz
2007-03-03 10:46       ` Alpár Jüttner [this message]
2007-03-03 11:34         ` Nick Roberts
2007-03-03 13:00           ` Alpár Jüttner
2007-03-03 14:36             ` Alpár Jüttner
2007-03-03 19:24               ` Nick Roberts
2007-03-05 12:39           ` Daniel Jacobowitz
2007-03-01 17:56     ` Brian Dessent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1172864572.4272.21.camel@mikro.mikro \
    --to=alpar@cs.elte.hu \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox