From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Handle broken CFI for signal trampolines in libc on amd64-linux
Date: Sat, 22 Nov 2008 23:56:00 -0000 [thread overview]
Message-ID: <200811221530.mAMFUawt026327@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <11706.86.86.3.213.1227267599.squirrel@webmail.xs4all.nl> from "Mark Kettenis" at Nov 21, 2008 12:39:59 PM
Mark Kettenis wrote:
> > On Fri, Nov 21, 2008 at 02:33:29AM +0100, Ulrich Weigand wrote:
> > > Anyway, while it is certainly good that this is fixed, I'm still
> > > wondering why we should rely on that when we have a hard-coded
> > > sigtramp detector that should be working just fine under any
> > > circumstances.
> >
> > I think that one reason was the extra work of the signal handler
> > sniffer. The amd64 one doesn't do much for named functions, though,
> > and functions with CFI are likely to be named. I suggest asking
> > Mark Kettenis's opinion.
>
> My memory is a bit hazy on this, but I think the idea was that the signal
> frame unwinder would only be used for older versions of linux/glibc that
> don't provide the necessary CFI, and that newer versions would provide
> correct CFI which would give the kernel/glibc people complete freedom on
> how to implement signal frames. As such, I'm inclined to say "no" to your
> diff.
OK, fair enough. As the bug is really in my copy of glibc anyway, I'll
withdraw my patch.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2008-11-22 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 19:19 Mark Kettenis
2008-11-22 23:56 ` Ulrich Weigand [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 15:01 Ulrich Weigand
2008-11-21 15:16 ` Daniel Jacobowitz
2008-11-21 18:12 ` Ulrich Weigand
2008-11-21 18:47 ` Daniel Jacobowitz
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=200811221530.mAMFUawt026327@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--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