From: Aurelien Jarno <aurelien@aurel32.net>
To: Tristan Gingold <gingold@adacore.com>
Cc: Nick Clifton <nickc@redhat.com>,
binutils Development <binutils@sourceware.org>
Subject: Re: Ping [Patch v2] bfd elfxx-ia64: share code between elf32 and elf64
Date: Sat, 09 Jul 2011 18:18:00 -0000 [thread overview]
Message-ID: <20110709165229.GA8780@hall.aurel32.net> (raw)
In-Reply-To: <DBD073AB-4CE9-4EC6-A3F1-CFE5483A6EFD@adacore.com>
On Wed, Jul 06, 2011 at 08:45:56AM +0200, Tristan Gingold wrote:
>
> On Jul 5, 2011, at 8:29 PM, Aurelien Jarno wrote:
>
> > Hello Tristan,
>
> [...]
>
> > This patch seems to break libc on ia64. ld-2.13.so produced with
> > binutils using this patch works when called as a standalone, but just
> > segfault when used with other binaries:
>
> [...]
>
> > I don't know what is the best way to proceed for debugging this issue. I
> > can provide you the correct and the broken ld.so if it can help.
>
> This patch shouldn't have made any functional change, but ...
>
> It would be useful if you could send (either directly to me or just open a bugzilla entry) *all* the object files required to build
> ld.so and the 'ld' command line to build it.
This is now done in bugzilla entry 12978.
Thanks,
Aurelien
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2011-07-09 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 12:56 [Patch] " Tristan Gingold
2011-05-17 13:04 ` H.J. Lu
2011-05-17 13:10 ` Tristan Gingold
2011-05-17 13:15 ` H.J. Lu
2011-05-17 15:12 ` [Patch v2] " Tristan Gingold
2011-05-23 8:00 ` Ping " Tristan Gingold
2011-05-24 13:50 ` Nick Clifton
2011-05-24 14:17 ` Tristan Gingold
2011-05-25 8:07 ` Nick Clifton
2011-05-25 12:03 ` Tristan Gingold
2011-07-05 19:06 ` Aurelien Jarno
2011-07-06 7:00 ` Tristan Gingold
2011-07-09 18:18 ` Aurelien Jarno [this message]
2011-07-10 11:53 ` Andreas Schwab
2011-07-11 16:20 ` H.J. Lu
2011-07-25 13:35 ` Tristan Gingold
2011-05-17 13:08 ` [Patch] " Andreas Schwab
2011-05-17 13:11 ` Tristan Gingold
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=20110709165229.GA8780@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=binutils@sourceware.org \
--cc=gingold@adacore.com \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).