From: Nick Clifton <nickc@redhat.com>
To: James Lemke <jwlemke@wasabisystems.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: intermittent 0-length for .note.gnu.arm.ident
Date: Thu, 20 Apr 2006 14:40:00 -0000 [thread overview]
Message-ID: <44476AEF.4060903@redhat.com> (raw)
In-Reply-To: <1145470462.6397.89.camel@winch.thelemkes.ca>
Hi James,
> If I manually re-compile one of the 0-length .o's, it always produces a
> section with 0x1c length. As does a make in that directory. But a
> top-level make gives the random sometimes 0-length note sections.
This sounds like memory corruption of some kind. I would suggest
enabling memory debugging if you have that support available, or else
adding some debugging of your own.
> arm_add_note() gets called with the same parms for both zero & non-zero
> cases. So what would cause the contents to disappear?
Note - the arm_add_note() function was removed a while ago, so you may
find that upgrading to newer binutils sources will solve this problem
for you.
Cheers
Nick
next prev parent reply other threads:[~2006-04-20 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 1:47 James Lemke
2006-04-20 14:40 ` Nick Clifton [this message]
2006-04-28 18:41 ` James Lemke
2006-04-29 14:51 ` James E Wilson
2006-05-01 5:35 ` Alan Modra
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=44476AEF.4060903@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jwlemke@wasabisystems.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).