This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] keeping convenience variables (take 2)
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Andrew STUBBS <andrew dot stubbs at st dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 22 Nov 2005 00:03:26 +0200
- Subject: Re: [PATCH] keeping convenience variables (take 2)
- References: <4381DC75.80800@st.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.