From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 12/13] Document "no debug info debugging" improvements
Date: Thu, 13 Jul 2017 16:14:00 -0000 [thread overview]
Message-ID: <53b1b51f-c8c9-cc5a-d846-3a92262590bf@redhat.com> (raw)
In-Reply-To: <831spkibka.fsf@gnu.org>
On 07/13/2017 04:47 PM, Eli Zaretskii wrote:
> Thanks, this is okay with a minor comment:
>
>> +includes no debug information, @value{GDBN} says @w{@samp{'var' has
>> +unknown type; cast it to its declared type}}. @xref{Symbols, unknown
>> +type}, for more about unknown types. If you cast the variable to its
>> +declared type, @value{GDBN} gets the variable's value using the
>> +cast-to type as the variable's type. For example, in a C program:
>> +
>> +@smallexample
>> + (@value{GDBP}) p var
>> + 'var' has unknown type; cast it to its declared type
>> + (@value{GDBP}) p (float) var
>> + $1 = 3.14
>> +@end smallexample
>
> Since you have an example showing the error message, repeating that in
> the text is redundant. Moreover, it will almost certainly cause an
> overfull hbox. Instead, I would just say
>
> If you try to inspect the type of a (global) variable for which
> @value{GDBN} has no type information, @value{GDBN} displays an error
> message.
>
...
> Same here.
Thanks, good idea. Meanwhile, the v2 of the docs are a bit
different in the "calling functions" part since they describe different
behavior. I'll apply that change to the v2 version, and resend it.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-07-13 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 2:19 [PATCH 00/13] No-debug-info debugging improvements Pedro Alves
2017-07-13 2:19 ` [PATCH 02/13] Introduce OP_VAR_MSYM_VALUE Pedro Alves
2017-07-13 2:19 ` [PATCH 07/13] Stop assuming no-debug-info variables have type int Pedro Alves
2017-07-13 2:19 ` [PATCH 08/13] Eliminate UNOP_MEMVAL_TLS Pedro Alves
2017-07-13 2:19 ` [PATCH 01/13] Stop assuming no-debug-info functions return int Pedro Alves
2017-07-13 2:19 ` [PATCH 03/13] Make ptype/whatis print function name of functions with no debug info too Pedro Alves
2017-07-13 2:19 ` [PATCH 04/13] evaluate_subexp_standard: Eliminate one goto Pedro Alves
2017-07-13 2:27 ` [PATCH 06/13] evaluate_subexp_standard: Factor out OP_VAR_VALUE handling Pedro Alves
2017-07-13 2:27 ` [PATCH 09/13] Handle "p S::method()::static_var" in the C++ parser Pedro Alves
2017-07-13 2:28 ` [PATCH 05/13] evaluate_subexp_standard: Remove useless assignments Pedro Alves
2017-07-13 2:28 ` [PATCH 11/13] Make "p S::method() const::static_var" work too Pedro Alves
2017-07-13 2:28 ` [PATCH 12/13] Document "no debug info debugging" improvements Pedro Alves
2017-07-13 11:09 ` [PATCH 13/13] " Pedro Alves
2017-07-13 13:51 ` Pedro Alves
2017-07-13 13:54 ` Pedro Alves
2017-07-13 15:33 ` Pedro Alves
2017-07-13 15:47 ` [PATCH 12/13] " Eli Zaretskii
2017-07-13 16:14 ` Pedro Alves [this message]
2017-07-13 2:29 ` [PATCH 12/13] Fix calling prototyped functions via function pointers Pedro Alves
2017-07-13 2:29 ` [PATCH 10/13] Handle "p 'S::method()::static_var'" (quoted) in symbol lookup Pedro Alves
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=53b1b51f-c8c9-cc5a-d846-3a92262590bf@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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