From: Eli Zaretskii <eliz@gnu.org>
To: "Rob Quill" <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Command File Scope Checking
Date: Tue, 24 Oct 2006 04:21:00 -0000 [thread overview]
Message-ID: <uslheuyx9.fsf@gnu.org> (raw)
In-Reply-To: <baf6008d0610231408o397e673vb5d00aca7c6b7a8a@mail.gmail.com> (rob.quill@gmail.com)
> Date: Mon, 23 Oct 2006 22:08:19 +0100
> From: "Rob Quill" <rob.quill@gmail.com>
>
> 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?
Why do you need to ``deal'' with that? I guess I don't understand
your problem, because I don't see any reason to care about such a
situation: at most, GDB will print an error message.
Can you show a small GDB script similar to what you use, and tell what
happens when a variable goes out of scope and how does that interfere
with the script?
next prev parent reply other threads:[~2006-10-24 4:21 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
2006-10-24 4:21 ` Eli Zaretskii [this message]
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=uslheuyx9.fsf@gnu.org \
--to=eliz@gnu.org \
--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