Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add switch to disable DWARF stack unwinders
Date: Fri, 13 Jul 2018 13:54:00 -0000	[thread overview]
Message-ID: <83muuvckcd.fsf@gnu.org> (raw)
In-Reply-To: <20180713134629.27011-1-andrew.burgess@embecosm.com> (message	from Andrew Burgess on Fri, 13 Jul 2018 14:46:29 +0100)

> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Fri, 13 Jul 2018 14:46:29 +0100
> 
> Add a maintenance command to disable the DWARF stack unwinders.
> Normal users would not need this feature, but it is useful to allow
> extended testing of fallback stack unwinding strategies, for example,
> prologue scanners.

Thanks.

> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -7,6 +7,12 @@
>    can be passed using the '[ADDRESS]:PORT' notation, or the regular
>    'ADDRESS:PORT' method.
>  
> +* New commands
> +
> +maint set dwarf unwinders (on|off)
> +maint show dwarf unwinders
> +  Control whether DWARF unwinders can be used.
> +
>  *** Changes in GDB 8.2

OK for this part.

> +@cindex DWARF frame unwinders
> +Many targets that support DWARF debugging use @value{GDBN}'s DWARF
> +frame unwinders to build the backtrace.  Many of these targets will
> +also have a second mechanism for building the backtrace for use in
> +cases where DWARF information is not available, this second mechanism
> +is often an analysis of a functions prologue.
                             ^^^^^^^^^^^^^^^^^^
I think you meant "function's prologue" there.

The documentation parts are OK with the above nit fixed.


  reply	other threads:[~2018-07-13 13:54 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 [this message]
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
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=83muuvckcd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.burgess@embecosm.com \
    --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