From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ping: [patch 1/6] PIE: Attach binary even after re-prelinked underneath
Date: Mon, 05 Jul 2010 17:49:00 -0000 [thread overview]
Message-ID: <20100705174920.GE2595@adacore.com> (raw)
In-Reply-To: <20100705172230.GA23280@host0.dyn.jankratochvil.net>
> I believe one should be looking at some two `readelf -Wa' dumps of an
> executable with two prelink addresses while checking this code so it should be
> apparent during real updates of that code.
That makes sense.
I look forward to the patches series being checked in...
--
Joel
next prev parent reply other threads:[~2010-07-05 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:30 [patch 1/6]: " Jan Kratochvil
2010-03-29 16:15 ` [patch 1/6]: PIE: Attach binary even after re-prelinked underneath [repost] Jan Kratochvil
2010-06-09 15:08 ` ping: [patch 1/6] PIE: Attach binary even after re-prelinked underneath Jan Kratochvil
2010-06-29 17:49 ` Joel Brobecker
2010-07-04 10:17 ` Jan Kratochvil
2010-07-05 17:06 ` Joel Brobecker
2010-07-05 17:22 ` Jan Kratochvil
2010-07-05 17:49 ` Joel Brobecker [this message]
2010-07-05 18:09 ` Jan Kratochvil
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=20100705174920.GE2595@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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