Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add switch to disable DWARF stack unwinders
Date: Tue, 17 Jul 2018 13:36:00 -0000	[thread overview]
Message-ID: <d3d94f50-cc0f-1cb2-2e6d-9949c79fe7ef@redhat.com> (raw)
In-Reply-To: <20180713134629.27011-1-andrew.burgess@embecosm.com>

On 07/13/2018 02:46 PM, Andrew Burgess wrote:
> 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.

I think a command to enable/disable unwinders is good, especially if
it supports all kinds of unwinders by name, but I thought I'd
also mention that the last time prologue testing came up, we ended up
with targeted unit tests.  See aarch64_analyze_prologue_test,
git commit 4d9a9006139d,
<https://sourceware.org/ml/gdb-patches/2016-12/msg00024.html>.

Thanks,
Pedro Alves


  parent reply	other threads:[~2018-07-17 13:36 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
2018-07-17 13:36 ` Pedro Alves [this message]
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=d3d94f50-cc0f-1cb2-2e6d-9949c79fe7ef@redhat.com \
    --to=palves@redhat.com \
    --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