From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Evaluating an expression in a given scope
Date: Wed, 07 Sep 2005 13:15:00 -0000 [thread overview]
Message-ID: <20050907131434.GB2963@nevyn.them.org> (raw)
In-Reply-To: <dfmn2o$r1t$1@sea.gmane.org>
On Wed, Sep 07, 2005 at 04:39:52PM +0400, Vladimir Prus wrote:
>
> Hello!
>
> Does gdb provides a clean way to evaluate an expression in a given scope
> (file:line)?
No, not really. File:line doesn't match unambiguously to scope,
either, so it's not clear what the interface should look like... I
think I'd use $pc instead.
> I think I can do this with:
>
> tbreak foo.cpp:100
> jump foo.cpp:100
> display g
> jump <previous source position>
>
> but I have concerns about this being reliable method.
... eww... I suppose that'd work.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-07 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 12:44 Vladimir Prus
2005-09-07 13:15 ` Daniel Jacobowitz [this message]
2005-09-07 13:50 ` Vladimir Prus
2005-09-07 13:53 ` Daniel Jacobowitz
2005-09-07 13:57 ` Daniel Jacobowitz
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=20050907131434.GB2963@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).