From: Kees Cook <kees@outflux.net>
To: gdb-patches@sourceware.org
Subject: Re: status of PIE support?
Date: Thu, 08 May 2008 19:50:00 -0000 [thread overview]
Message-ID: <20080508181905.GL12850@outflux.net> (raw)
In-Reply-To: <20080508173720.GA26555@caradoc.them.org>
On Thu, May 08, 2008 at 01:37:20PM -0400, Daniel Jacobowitz wrote:
> On Wed, May 07, 2008 at 10:45:26PM -0700, Kees Cook wrote:
> > Hello! I'm curious what the current status PIE support is?
>
> No status that I know of. No one has been working on it for FSF GDB.
>
> Jan may know more since he maintains the Red Hat packaging.
I'd love to help get it into mainline, but my knowledge of gdb internals
is rather poor currently. I figure I can help perhaps with coordination
and certainly with testing.
Jan, would getting PIE support into mainline gdb be something you would
have time for?
> - the submitter has to be able to justify any line of the patch that
> does not make sense to the reviewer
This is probably where I'd get hung up, shouting "it's magic!" :)
> time to do it. A good way to handle bits you don't understand is
> to remove them and see what breaks; often this isn't practical,
> but when it is it's a sign of good tests :-)
Yeah, I assume that I'll end up learning gdb internals eventually, and be
a bit more helpful then, but that won't be in the near-term. That said,
it's been 5 years since Elena Zannoni's original work, so I'm hoping
some folks will step up and help review the existing patches with me --
they clearly have some merit.
Thanks!
-Kees
--
Kees Cook @outflux.net
next prev parent reply other threads:[~2008-05-08 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 16:10 Kees Cook
2008-05-08 19:00 ` Daniel Jacobowitz
2008-05-08 19:50 ` Kees Cook [this message]
2008-05-08 20:22 ` 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=20080508181905.GL12850@outflux.net \
--to=kees@outflux.net \
--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