From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: nickrob@snap.net.nz
Cc: drow@false.org, gdb@sources.redhat.com
Subject: Re: stepping over longjmp
Date: Sat, 05 Aug 2006 12:40:00 -0000 [thread overview]
Message-ID: <200608051239.k75CdwTH005284@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <17619.64925.33169.651834@kahikatea.snap.net.nz> (message from Nick Roberts on Sat, 5 Aug 2006 14:08:29 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 5 Aug 2006 14:08:29 +1200
>
> > > > Does export LD_POINTER_GUARD=0 make a difference?
> > >
> > > No.
> >
> > Hmm, then it must be something else.
>
> Actually, it does work if it's set for both compilation and execution. I also
> updated to 2.4-8 (from 2.4-4). I don't know if that was necessary but on the
> Internet I saw:
>
> > You can disable the encryption using the LD_POINTER_GUARD environment
> > variable. Unfortunately the glibc version so far in FC5 has a little
> > bug. The next update will allow you to specify LD_POINTER_GUARD=0.
> >
> > But this is really the wrong solution. The program should be
> > rewritten
> > to use __builtin_frame_address (see the gcc manual).
> >
> > -- Ulrich Drepper
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.
Mark
next prev parent reply other threads:[~2006-08-05 12:40 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 [this message]
2006-08-05 14:07 ` 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=200608051239.k75CdwTH005284@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--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