Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: nickrob@snap.net.nz, gdb@sources.redhat.com
Subject: Re: stepping over longjmp
Date: Sat, 05 Aug 2006 14:07:00 -0000	[thread overview]
Message-ID: <20060805140728.GA27405@nevyn.them.org> (raw)
In-Reply-To: <200608051239.k75CdwTH005284@elgar.sibelius.xs4all.nl>

On Sat, Aug 05, 2006 at 02:39:58PM +0200, Mark Kettenis wrote:
> Unfortunately Ulrich's argument doesn't hold for GDB.  But if we can
> get at the "cookie" that's used to encrypt the addess, it should be
> possible to undo the encryption.  Lookes like the cookie is somewhere
> in thread local storage.  I'll see if I can come up with a way to
> access it.

It varies from platform to platform.  There's actually two cookies (one
for "pointers" and one for the GCC stack protection), and while the
stack protection pointer is an ABI, the pointer protection cookie is
considered glibc internal and might move around.  And what's protected
with it also varies from architecture to architecture, and version to
version.

I'm hoping that you can make an educated guess about where to find it
anyway :-)  Alternatively, maybe they'd be open to a debugging
interface.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-08-05 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  8:13 Nick Roberts
2006-08-04 13:19 ` Daniel Jacobowitz
2006-08-04 22:20   ` Nick Roberts
2006-08-04 23:45     ` Daniel Jacobowitz
2006-08-05  2:10       ` Nick Roberts
2006-08-05  2:33         ` Daniel Jacobowitz
2006-08-05  6:10           ` Nick Roberts
2006-08-05 12:28             ` Eli Zaretskii
2006-08-05 12:40         ` Mark Kettenis
2006-08-05 14:07           ` Daniel Jacobowitz [this message]

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=20060805140728.GA27405@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=nickrob@snap.net.nz \
    /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