Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] keeping convenience variables (take 2)
Date: Tue, 22 Nov 2005 04:58:00 -0000	[thread overview]
Message-ID: <uhda5y7yp.fsf@gnu.org> (raw)
In-Reply-To: <4381DC75.80800@st.com> (message from Andrew STUBBS on Mon, 21 	Nov 2005 14:40:53 +0000)

> Date: Mon, 21 Nov 2005 14:40:53 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> 
> +@value{GDBN} commands that wipe the symbol table, such as @samp{file} and
> +@samp{symbol-file}, cause problems for convenience variables---their types
> +may be lost so their values may become meaningless.  @value{GDBN} tries to
> +avoid this by selecting a type from the new symbol table (if any).  If a
> +suitable type does not exist (at the time the variable is accessed) then
> +@value{GDBN} will show the value as @code{void} until the type becomes
> +available once more.  The @samp{show convenience} command will tag these
> +variables with @samp{<type '...' unknown>}.
                               ^^^
Please use @dots{} here instead of a literal "..." (the former
produces better results in print).

Also, please give an example of a variable whose definition makes it
dependant on the symbol table.  Since only that kind of convenience
variables is prone to this problem, I think it's important that we
show the reader when such a problem can happen.

Other than that, this part is approved.  Thanks.


  reply	other threads:[~2005-11-21 22:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 22:05 Andrew STUBBS
2005-11-22  4:58 ` Eli Zaretskii [this message]
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
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=uhda5y7yp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.stubbs@st.com \
    --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