From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: Remove support for old mangling schemes
Date: Wed, 09 Jan 2019 15:59:00 -0000 [thread overview]
Message-ID: <0da7933d5fb99c0c390acb5482cdcde7@polymtl.ca> (raw)
In-Reply-To: <83h8ehj0wi.fsf@gnu.org>
On 2019-01-09 10:39, Eli Zaretskii wrote:
>> From: Simon Marchi <simon.marchi@polymtl.ca>
>> Cc: Simon Marchi <simon.marchi@ericsson.com>
>> Date: Tue, 8 Jan 2019 23:50:32 -0500
>>
>> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
>> index 4bca933195c9..ffc702937b7a 100644
>> --- a/gdb/doc/gdb.texinfo
>> +++ b/gdb/doc/gdb.texinfo
>> @@ -10703,31 +10703,9 @@ or demangled form.
>> @cindex symbol decoding style, C@t{++}
>> @kindex set demangle-style
>> @item set demangle-style @var{style}
>> -Choose among several encoding schemes used by different compilers to
>> -represent C@t{++} names. The choices for @var{style} are currently:
>> -
>> -@table @code
>> -@item auto
>> -Allow @value{GDBN} to choose a decoding style by inspecting your
>> program.
>> -This is the default.
>
> Are we removing 'auto' as well? If not, why do we want to un-document
> it?
I decided to remove the list of possible values and refer to the
in-process help, this way we don't have to keep it up to date (as you
might notice, the list was incomplete). But since the value "auto" is
special, I agree we should mention it. Is it fine if I add this
sentence?
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index ffc702937b7..4a00834d0bf 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -10705,7 +10705,8 @@ or demangled form.
@item set demangle-style @var{style}
Choose among several encoding schemes used by different compilers to
represent
C@t{++} names. If you omit @var{style}, you will see a list of
possible
-formats.
+formats. The default value is @var{auto}, which lets @value{GDBN}
choose a
+decoding style by inspecting your program.
@item show demangle-style
Display the encoding style currently in use for decoding C@t{++}
symbols.
Simon
next prev parent reply other threads:[~2019-01-09 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 23:22 [PATCH] " Simon Marchi
2019-01-09 3:38 ` Eli Zaretskii
2019-01-09 4:12 ` Simon Marchi
2019-01-09 16:54 ` Tom Tromey
2019-01-09 4:50 ` [PATCH v2] " Simon Marchi
[not found] ` <83h8ehj0wi.fsf@gnu.org>
2019-01-09 15:59 ` Simon Marchi [this message]
2019-01-09 16:14 ` Eli Zaretskii
2019-01-09 16:18 ` Simon Marchi
2019-01-09 17:02 ` Keith Seitz
2019-01-09 18:08 ` Simon Marchi
[not found] ` <e8dcdefe-5f8f-6e1b-116f-f4bf166d55c6@redhat.com>
2019-01-09 4:36 ` [PATCH] " Simon Marchi
2019-01-09 16:59 ` Tom Tromey
2019-01-09 18:53 ` 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=0da7933d5fb99c0c390acb5482cdcde7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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