From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Handle broken CFI for signal trampolines in libc on amd64-linux
Date: Fri, 21 Nov 2008 18:47:00 -0000 [thread overview]
Message-ID: <20081121014156.GA19240@caradoc.them.org> (raw)
In-Reply-To: <200811210133.mAL1XTSF010875@d12av02.megacenter.de.ibm.com>
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-21 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2008-11-21 19:19 Mark Kettenis
2008-11-22 23:56 ` Ulrich Weigand
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=20081121014156.GA19240@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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