Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: andrew.stubbs@st.com, gdb-patches@sources.redhat.com
Subject: Re: [SH][PATCH] Disable ABI frame sniffer
Date: Fri, 11 Nov 2005 10:31:00 -0000	[thread overview]
Message-ID: <20051110230858.GA3195@nevyn.them.org> (raw)
In-Reply-To: <200511102259.jAAMxdJC029449@elgar.sibelius.xs4all.nl>

On Thu, Nov 10, 2005 at 11:59:39PM +0100, Mark Kettenis wrote:
> Ah there's your real problem.  The unwinder walks off the stack and at
> that point concludes the stack is thrashed.  This is a recurring
> problem on many platforms, especially when threads are involved.  It
> might be possible to detect the end of the stack on your platform and
> teach the fallback unwinder about it.  That might involve some changes
> to the threads library and/or crt0 though, to make it mark the end of
> the stack properly.  It'd also be great to have a way to encode the
> end of the stack in CFI.  Unfortunately there has been quite a bit of
> talk about this, but nobody has implemeneted anything yet.

How short your memory... :-)

  http://sources.redhat.com/ml/gdb-patches/2005-03/msg00021.html

There's no way in GCC to annotate a function with this property, and it
appears that the thread-start routine in Andrew's OS is written in C,
so I don't know if it helps.

The fp == 0 and pc == 0 checks are one level off for stopping this, as
I recall.  A cleverer solution to that might be possible.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-11-10 23:09 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
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 [this message]
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=20051110230858.GA3195@nevyn.them.org \
    --to=drow@false.org \
    --cc=andrew.stubbs@st.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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