From: Jim Blandy <jimb@codesourcery.com>
To: "Rob Quill" <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Command File Scope Checking
Date: Mon, 23 Oct 2006 22:23:00 -0000 [thread overview]
Message-ID: <m33b9e65a3.fsf@codesourcery.com> (raw)
In-Reply-To: <baf6008d0610231408o397e673vb5d00aca7c6b7a8a@mail.gmail.com> (Rob Quill's message of "Mon, 23 Oct 2006 22:08:19 +0100")
"Rob Quill" <rob.quill@gmail.com> writes:
> On 23/10/06, Daniel Jacobowitz <drow@false.org> wrote:
>> On Mon, Oct 23, 2006 at 09:15:31PM +0100, Rob Quill wrote:
>> > On 23/10/06, Eli Zaretskii <eliz@gnu.org> wrote:
>> > >> Date: Mon, 23 Oct 2006 11:45:23 +0100
>> > >> From: "Rob Quill" <rob.quill@gmail.com>
>> > >>
>> > >> Is it possible to check if a variable is in scope when using a command
>> > >> file, because I don't want control to return to GDB when a variable
>> > >> goes out of scope, so I would like to know if a variable is in scope
>> > >> before I check the value of it.
>> > >
>> > > (gdb) info address foobar
>> > > No symbol "foobar" in current context.
>> >
>> > So is it possible to check the result of doing info address foobar,
>> > whilst still in the command file? So that if it is out of scope the
>> > script can do action B instead of action A?
>>
>> No, this sort of thing is not possible in the current GDB scripting
>> interface. Yet, anyway.
>
> In that case, I'm in need of some advice. I was thinking it would work
> something like this:
>
> Write program that given an LTL formula, writes a GDB command file
> representing the automaton and stepping through the code, checking
> values of variables and using these to make transitions. Pipe the
> output to a file and then analyse the file is some way to decide if
> the condition had been met.
>
> But if I am stepping through the code, and a variable goes out of
> scope, how do you suggest I go about dealing with this?
I'm surprised that your LTL automaton would need to check this. If
your conditions are referring to variables that are out of scope, then
something strange is going on.
next prev parent reply other threads:[~2006-10-23 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 10:45 Rob Quill
2006-10-23 14:31 ` Eli Zaretskii
[not found] ` <baf6008d0610231314k2e8d512ckf89dcb6873ba70cb@mail.gmail.com>
2006-10-23 20:15 ` Rob Quill
2006-10-23 20:20 ` Daniel Jacobowitz
2006-10-23 21:08 ` Rob Quill
2006-10-23 22:23 ` Jim Blandy [this message]
2006-10-24 4:21 ` Eli Zaretskii
2006-10-24 9:52 ` 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=m33b9e65a3.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=rob.quill@gmail.com \
/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