From: "Rob Quill" <rob.quill@gmail.com>
To: gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Scope Checking Patch
Date: Sun, 10 Jun 2007 20:54:00 -0000 [thread overview]
Message-ID: <baf6008d0706101354i701690d9ped8dc9ab6e3ccbcc@mail.gmail.com> (raw)
Hi all,
This is the first patch I have ever submitted to an open source
project, so I'm a little bit unsure of the process. The patch adds the
ability to check if a variable is in scope, as descibed here:
http://sourceware.org/ml/gdb/2006-11/msg00149.html
I have attached the diffs for the two files I've changed. However, I
am seeing some regressions against the current cvs, which I can't
understand, so I was wondering if a) the regressions happen for anyone
esle? (which presumably it does), b) if anyone could offer any
suggestions as to the cause, and c) give thier opinions on the patch.
The patch allows the scope of constants, variables and variables in
classes/structures, by using $in_scope(variable_name) as an
expression, with value 1 if variable_name is in scope and 0 if it is
not.
Any help and thoughts you can offer is much appreciated.
Thanks,
Rob
next reply other threads:[~2007-06-10 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 20:54 Rob Quill [this message]
2007-06-10 20:55 ` Rob Quill
2007-06-11 17:12 ` Jim Blandy
2007-06-11 17:31 ` Rob Quill
2007-06-13 13:33 ` Rob Quill
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=baf6008d0706101354i701690d9ped8dc9ab6e3ccbcc@mail.gmail.com \
--to=rob.quill@gmail.com \
--cc=gdb-patches@sourceware.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