From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: joseph@codesourcery.com
Cc: drow@false.org, gdb-patches@sourceware.org,
pedro@codesourcery.com, uweigand@de.ibm.com
Subject: Re: RFC: Longjmp vs LD_POINTER_GUARD revisited
Date: Sun, 15 Nov 2009 21:52:00 -0000 [thread overview]
Message-ID: <200911152148.nAFLmYPK018249@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0911151833510.28152@digraph.polyomino.org.uk> (joseph@codesourcery.com)
> Date: Sun, 15 Nov 2009 18:38:19 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
>
> On Sun, 15 Nov 2009, Daniel Jacobowitz wrote:
>
> > should continue stepping. For x86_64 glibc, the magic name is
> > "__longjmp". Otherwise, we do a frame check as before.
>
> Nowadays you may need to handle ____longjmp_chk for glibc 2.11 as well.
> Because distribution compilers may or may not enable _FORTIFY_SOURCE by
> default, I suppose in principle the tests should be run explicitly with
> different settings.
Isn't it a bit ridiculous that glibc, which is a GNU project, makes
the life of GDB, another GNU project, so difficult?
next prev parent reply other threads:[~2009-11-15 21:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 17:35 Daniel Jacobowitz
2009-11-15 18:06 ` Eli Zaretskii
2009-11-15 18:30 ` Paul Pluzhnikov
2009-11-15 22:36 ` Daniel Jacobowitz
2009-11-15 23:06 ` Paul Pluzhnikov
2009-11-16 14:37 ` Daniel Jacobowitz
2009-11-16 14:55 ` Pedro Alves
2009-11-16 14:56 ` Pedro Alves
2009-11-16 15:05 ` Pedro Alves
2009-11-16 17:50 ` Daniel Jacobowitz
2009-11-15 18:39 ` Joseph S. Myers
2009-11-15 21:52 ` Mark Kettenis [this message]
2009-11-15 22:37 ` Daniel Jacobowitz
2009-11-16 15:15 ` Frank Ch. Eigler
2009-11-16 15:40 ` Paul Pluzhnikov
2009-11-16 15:43 ` Paul Pluzhnikov
2009-11-16 16:19 ` Mark Kettenis
2009-11-16 15:59 ` Mark Kettenis
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=200911152148.nAFLmYPK018249@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=pedro@codesourcery.com \
--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