From: "Rob Quill" <rob.quill@gmail.com>
To: gdb@sourceware.org
Subject: Checking variable scope
Date: Wed, 29 Nov 2006 13:20:00 -0000 [thread overview]
Message-ID: <baf6008d0611290520h47f68f22xde49cc235143925f@mail.gmail.com> (raw)
In-Reply-To: <baf6008d0611290519i4e25c51bt865320b09c756ec8@mail.gmail.com>
On 28/11/06, Jim Blandy <jimb@codesourcery.com> wrote:
>
> "Rob Quill" <rob.quill@gmail.com> writes:
> > The aim would be to add a command to gdb, in_scope (or similar) which
> > can be used from a GDB script to check if a variable is in scope
> > without throwing an error if is isn't. As currently if I do "print a"
> > and a is not in scope then I get an error and the script stops, which
> > is fine. But even better would be if I were able to check if a was in
> > scope and only print (or do other things with it) if it was.
>
> Why don't you add a new expression operator, $in_scope(a), which
> evaluates to zero or one? You could just imitate the other code in
> the parser and expression evaluator, so this should be straightforward
> to implement, and then you could use it in GDB script conditional
> commands.
>
Could you elaborate on this a bit please? I'm not really sure what you
mean and how to go about implementing it.
Thanks,
Rob
next prev parent reply other threads:[~2006-11-29 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 11:32 Rob Quill
2006-11-22 19:10 ` Jim Blandy
2006-11-23 13:09 ` Rob Quill
2006-11-27 19:46 ` Jim Blandy
2006-11-28 11:47 ` Rob Quill
2006-11-28 19:43 ` Jim Blandy
[not found] ` <baf6008d0611290519i4e25c51bt865320b09c756ec8@mail.gmail.com>
2006-11-29 13:20 ` Rob Quill [this message]
2006-11-29 18:44 ` Jim Blandy
2006-11-29 19:06 ` Daniel Jacobowitz
2006-11-29 19:08 ` Jim Blandy
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=baf6008d0611290520h47f68f22xde49cc235143925f@mail.gmail.com \
--to=rob.quill@gmail.com \
--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