From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simark@simark.ca>,
Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add switch to disable DWARF stack unwinders
Date: Tue, 17 Jul 2018 13:23:00 -0000 [thread overview]
Message-ID: <41628b49-fed1-717e-2072-189270c7433d@redhat.com> (raw)
In-Reply-To: <d7d69ef5-3e11-4833-f760-0bf93d787038@simark.ca>
On 07/14/2018 10:39 PM, Simon Marchi wrote:
> On 2018-07-14 04:35 PM, Andrew Burgess wrote:
>>> I don't think this is necessary, if you leave the "show" callback to NULL,
>>> I think the message is clear enough:
>>>
>>> (gdb) maintenance show dwarf unwinders
>>> Whether the DWARF stack frame unwinders are used is on.
>>
>> I thought that was no longer the approved approach as the resulting
>> string is generated and not internationalised?
>
> Ah, I was not aware of that. If you got that from a trustworthy source, then
> I won't object :).
Here:
void
deprecated_show_value_hack (struct ui_file *ignore_file,
int ignore_from_tty,
struct cmd_list_element *c,
const char *value)
{
...
/* Print doc minus "show" at start. */
print_doc_line (gdb_stdout, c->doc + 5);
That "c->doc + 5" trick only works in English.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-07-17 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 13:46 Andrew Burgess
2018-07-13 13:54 ` Eli Zaretskii
2018-07-13 15:34 ` Tom Tromey
2018-07-13 22:37 ` Andrew Burgess
2018-07-13 22:57 ` Tom Tromey
2018-07-14 20:36 ` Andrew Burgess
2018-07-16 15:34 ` Tom Tromey
2018-07-14 1:11 ` Simon Marchi
2018-07-14 20:35 ` Andrew Burgess
2018-07-14 21:39 ` Simon Marchi
2018-07-17 13:23 ` Pedro Alves [this message]
2018-07-17 13:36 ` Pedro Alves
2018-07-25 15:18 ` [PATCHv2] " Andrew Burgess
2018-07-25 17:09 ` Eli Zaretskii
2018-07-25 20:07 ` Tom Tromey
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=41628b49-fed1-717e-2072-189270c7433d@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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