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

 > > > 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.

I'm not sure that I understand exactly what you're trying to do, but if
Daniel says it can't be done in GDB, then I dont think it can be done in
Emacs, as Emacs can only use the output that GDB gives it.

 >             For example how to obtain the file name of the currently
 > debugged line in emacs/gud/gdb?

This bit is straightforward: Emacs 21 uses --fullname option (although it is
hidden to the user).  For example, try:

gdb --fullname `prog'
(gdb) start

from the command line, then step a few times.  You'll see the current line,
that Emacs uses, get printed out.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-03-03 11:34 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
2007-03-03 11:34         ` Nick Roberts [this message]
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=17897.23824.618849.817120@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=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