From: James E Wilson <wilson@specifixinc.com>
To: Peter Steinmetz <steinmtz@us.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: gprof not happy with mainline output.
Date: Thu, 09 Sep 2004 00:15:00 -0000 [thread overview]
Message-ID: <1094688920.28347.60.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <OF3FED3FEF.57719CC6-ON86256F09.006BA56B-86256F09.006C0BD4@us.ibm.com>
On Wed, 2004-09-08 at 12:40, Peter Steinmetz wrote:
> I wondered about binutils as well. I'm running with binutils-2.15.
Perhaps binutils-2.15 is broken then. You might try using one of HJ's
binutils releases instead, e.g. 2.15.90.whatever.he.calls.it. Or try
using the binutils mainline, to see if maybe the problem has already
been fixed there. Binutils mainline is usually safe to use, unlike gcc
mainline.
I doubt this is a gcc problem. This is much more likely an internal
binutils problem with the string table (strtab) section merging
support. There is linker support for eliminating duplicate strings from
the string tables. I think were some bugs in this area that were fixed
a few months ago, but I don't know if the patches are in the
binutils-2.15 release.
You probably can see similar messages from anything else that tries to
read and parse an ELF object file, e.g. gdb, objdump, readelf, etc.
My PPC machine only has darwin installed on it, and binutils does not
support darwin, and my x86_64-linux machine is already busy with two
other builds, so I haven't tried to reproduce this.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
prev parent reply other threads:[~2004-09-09 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 21:38 Peter Steinmetz
2004-09-04 0:22 ` James E Wilson
2004-09-08 19:40 ` Peter Steinmetz
2004-09-09 0:15 ` James E Wilson [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=1094688920.28347.60.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=gcc@gcc.gnu.org \
--cc=steinmtz@us.ibm.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).