From: Jim Blandy <jimb@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com, Andrew STUBBS <andrew.stubbs@st.com>
Subject: Re: [RFC] Alternate approach to keeping convenience variables
Date: Mon, 23 Jan 2006 22:29:00 -0000 [thread overview]
Message-ID: <8f2776cb0601231429y38714c9bm830991b4b037ec70@mail.gmail.com> (raw)
In-Reply-To: <ud5k5e2xe.fsf@gnu.org>
On 12/10/05, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 9 Dec 2005 15:59:23 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Jim Blandy <jimb@red-bean.com>, gdb-patches@sources.redhat.com
> >
> > The tracepoint.c change is necessary for default.exp. To see why, try
> > this:
> > $ gdb
> > (gdb) show convenience
> > $trace_frame = -1
> > $tpnum = 0
> >
> > vs.
> > $ gdb /bin/ls
> > (gdb) show convenience
> > No debugger convenience variables now defined.
> > Convenience variables have names starting with "$";
> > use "set" as in "set $foo = 5" to define them.
> >
> > If you want the inconsistency resolve the other way round, please
> > holler.
>
> I understand that, with your change, GDB will behave as in the second
> example, even if no executable file was loaded yet, yes? If so, I'm
> for this change: I think GDB shouldn't show tracepoint-related
> variables unless tracepoints are actually being used.
[leaving lots of context in, since it's been a while]
The $trace_frame variable is set to -1 when GDB starts, which
indicates that there's no trace frame selected. I think it would be a
little more helpful for the variables to always exist: you can write
user-defined commands that give a reasonable error message, for
example. GDB doesn't have any way (?) to check whether a convenience
variable has been initialized yet.
next prev parent reply other threads:[~2006-01-23 22:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:05 [PATCH] keeping convenience variables (take 2) Andrew STUBBS
2005-11-22 4:58 ` Eli Zaretskii
2005-11-22 8:43 ` Jim Blandy
2005-11-22 19:27 ` Andrew STUBBS
2005-12-10 4:46 ` [RFC] Alternate approach to keeping convenience variables Daniel Jacobowitz
2005-12-10 5:07 ` Jim Blandy
2005-12-10 8:24 ` Daniel Jacobowitz
2005-12-10 22:20 ` Jim Blandy
2005-12-11 18:12 ` Eli Zaretskii
2005-12-11 19:17 ` Eli Zaretskii
2006-01-23 22:29 ` Jim Blandy [this message]
2006-01-24 11:44 ` Andrew STUBBS
2006-01-24 18:41 ` Jim Blandy
2006-01-24 18:43 ` Daniel Jacobowitz
2006-01-24 19:16 ` Jim Blandy
2006-01-24 19:24 ` Daniel Jacobowitz
2006-01-25 0:13 ` Jim Blandy
2006-01-24 19:45 ` Andrew STUBBS
2006-01-04 12:17 ` Andrew STUBBS
2006-01-04 17:00 ` Jim Blandy
2006-01-04 17:48 ` Andrew STUBBS
2006-01-04 18:37 ` Jim Blandy
2006-01-22 21:04 ` Daniel Jacobowitz
2006-01-22 21:31 ` Daniel Jacobowitz
2006-01-23 22:46 ` Jim Blandy
2006-01-27 17:53 ` Eli Zaretskii
2006-01-27 18:12 ` Jim Blandy
2006-01-27 18:29 ` Eli Zaretskii
2006-01-27 18:41 ` Joel Brobecker
2006-02-01 23:14 ` Daniel Jacobowitz
2006-02-02 4:18 ` Eli Zaretskii
2006-02-06 22:14 ` 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=8f2776cb0601231429y38714c9bm830991b4b037ec70@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=andrew.stubbs@st.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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