From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, simark@simark.ca, tom@tromey.com
Subject: Re: [PATCHv2] gdb: Add switch to disable DWARF stack unwinders
Date: Wed, 25 Jul 2018 17:09:00 -0000 [thread overview]
Message-ID: <83tvontf8r.fsf@gnu.org> (raw)
In-Reply-To: <20180725151842.6443-1-andrew.burgess@embecosm.com> (message from Andrew Burgess on Wed, 25 Jul 2018 16:18:42 +0100)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Andrew Burgess <andrew.burgess@embecosm.com>, Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>
> Date: Wed, 25 Jul 2018 16:18:42 +0100
>
> + add_setshow_boolean_cmd ("unwinders", class_obscure,
> + &dwarf2_frame_unwinders_enabled_p , _("\
> +Set whether the DWARF stack frame unwinders are used."), _("\
> +Show whether the DWARF stack frame unwinders are used."), _("\
> +When enabled the DWARF stack frame unwinders can be used for architectures\n\
> +that support the DWARF unwinders. Enabling the dwarf unwinders for an\n\
> +architecture that doesn't support them will have no effect."),
The last instance of "dwarf" should be up-cased.
Otherwise the documentation parts are OK. Thanks.
next prev parent reply other threads:[~2018-07-25 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 13:46 [PATCH] " 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
2018-07-17 13:36 ` Pedro Alves
2018-07-25 15:18 ` [PATCHv2] " Andrew Burgess
2018-07-25 17:09 ` Eli Zaretskii [this message]
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=83tvontf8r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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