From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Prelink.exp troubles
Date: Sat, 25 Mar 2006 07:02:00 -0000 [thread overview]
Message-ID: <20060325065736.GJ26748@nevyn.them.org> (raw)
In-Reply-To: <oru0a8sc3b.fsf@free.oliva.athome.lsd.ic.unicamp.br>
On Wed, Mar 08, 2006 at 09:20:24PM -0300, Alexandre Oliva wrote:
> On Mar 7, 2006, Daniel Jacobowitz <drow@false.org> wrote:
>
> > On Tue, Mar 07, 2006 at 02:02:40AM -0300, Alexandre Oliva wrote:
>
> >> Here's what I'm checking in, in the hopes that the archoring you
> >> suggested above is not needed, otherwise I'll take care of it in a
> >> subsequent patch.
>
> > Please fix the anchoring.
>
> In the following patch, that I'm checking in as obvious, I fix
> anchoring and also tidy up some code added in the original prelink
> patch, such that it's absolutely obvious that the l_addr field is
> properly initialized in all cases.
Belatedly, thanks for fixing this.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-03-25 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 20:05 Daniel Jacobowitz
2006-03-03 14:49 ` Alexandre Oliva
2006-03-06 18:38 ` Daniel Jacobowitz
2006-03-07 8:38 ` Alexandre Oliva
2006-03-07 19:34 ` Daniel Jacobowitz
2006-03-09 4:40 ` Alexandre Oliva
2006-03-25 7:02 ` 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=20060325065736.GJ26748@nevyn.them.org \
--to=drow@false.org \
--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