Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [SH][PATCH] Disable ABI frame sniffer
Date: Thu, 10 Nov 2005 04:27:00 -0000	[thread overview]
Message-ID: <20051110013122.GB11334@nevyn.them.org> (raw)
In-Reply-To: <43722DEF.8060300@st.com>

On Wed, Nov 09, 2005 at 05:12:15PM +0000, Andrew STUBBS wrote:
> Hi,
> 
> The attached patch adds a new sh-specific command:
> 
> set backtrace abi-sniffer
> 
> This command allows the ABI frame sniffer to be disabled. The default 
> state remains 'on', as it is now.

I had to look up what you meant by "ABI frame sniffer"; we normally
call this the prologue analyzer.

> With the ABI sniffer 'off' it is not possible to backtrace through code 
> that does not have CFI. On sh-elf, at least, there is always CFI when 
> there is debug info, so it is relatively rare that the ABI sniffer is 
> actually required.
> 
> I have not set the default to 'off' because that causes quite a number 
> of FAILs in the testsuite.

That should be a hint...

Obviously the SH maintainers have final say, but I strongly discourage
any patch along these lines.  If you want to improve the fallback
unwinder, go ahead.  If you want to add more generic tests to terminate
backtraces without annoying messages, we can discuss that.  But turning
it off is not viable.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-11-10  1:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 18:08 Andrew STUBBS
2005-11-10  0:17 ` Andreas Schwab
2005-11-10  3:30   ` Daniel Jacobowitz
2005-11-10 12:27     ` Andrew STUBBS
2005-11-10 14:24       ` Daniel Jacobowitz
2005-11-10  4:27 ` Daniel Jacobowitz [this message]
2005-11-10 13:36   ` Andrew STUBBS
2005-11-10 14:34     ` Daniel Jacobowitz
2005-11-10 23:09       ` Andrew STUBBS
2005-11-10 23:13         ` Andrew STUBBS
2005-11-11  0:10         ` Mark Kettenis
2005-11-11 10:31           ` Daniel Jacobowitz
2005-11-11 18:21           ` Andrew STUBBS
2005-11-11 10:35         ` Daniel Jacobowitz
2005-11-11 20:09           ` Andrew STUBBS
2005-11-13 18:57             ` Daniel Jacobowitz
2005-11-13 23:58               ` Jim Blandy
2005-11-23 19:52               ` Andrew STUBBS
2005-11-24 22:48                 ` Andrew STUBBS
2005-11-24 23:42                   ` Mark Kettenis
2005-11-10 11:11 ` Eli Zaretskii

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=20051110013122.GB11334@nevyn.them.org \
    --to=drow@false.org \
    --cc=andrew.stubbs@st.com \
    --cc=gdb-patches@sources.redhat.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