From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
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:12:00 -0000 [thread overview]
Message-ID: <200811210133.mAL1XTSF010875@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20081120235151.GA12123@caradoc.them.org> from "Daniel Jacobowitz" at Nov 20, 2008 06:51:51 PM
Daniel Jacobowitz wrote:
> On Fri, Nov 21, 2008 at 12:38:11AM +0100, Ulrich Weigand wrote:
> > Unfortunately even if I use the dwarf_signal_frame_p hook to have the
> > DWARF-2 sniffer recognize a SIGTRAMP_FRAME, it still doesn't work as
> > the __restore_rt CFI (at least in my glibc) only describes the unwind
> > effects as if it were a regular function, without taking into account
> > the restoring of registers by the sigreturn system call.
>
> What version of glibc is this? It was fixed two years ago this month:
Well, it's the system glibc of my openSUSE 10.2 install (based on
a 2006-10-12 glibc-2.5 snapshot), which is indeed somewhat over two
years old. I guess I could update to a more recent distro one of
these days ...
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.
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-21 1:34 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 [this message]
2008-11-21 18:47 ` Daniel Jacobowitz
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=200811210133.mAL1XTSF010875@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--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