public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Paul Nash <nashpaulr@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: binutils-2.17: --cref broken? Extra warnings and corrupted data
Date: Mon, 17 Jul 2006 02:03:00 -0000	[thread overview]
Message-ID: <20060717020350.GH18571@bubble.grove.modra.org> (raw)
In-Reply-To: <e6f772530607152341w5456bdfbm939c9f4b6a76d1f1@mail.gmail.com>

On Sat, Jul 15, 2006 at 11:41:23PM -0700, Paul Nash wrote:
> I determined with gdb that at the time add_cref is called,
> h->root.string is a valid string pointer.  What's causing the problem
> is that later when the cref table is output, the underlying memory
> behind that pointer has been corrupted. In one case I looked at, a
> later bfd_zalloc call memset's all the memory around that string to 0.

Try reverting HJ's 2006-04-25 patch.
http://sources.redhat.com/ml/binutils/2006-04/msg00095.html

Please let us know if this fixes the problem for you.  There are likely
to be other serious problems besides the --cref one.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2006-07-17  2:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16  6:41 Paul Nash
2006-07-17  2:03 ` Alan Modra [this message]
2006-07-17 22:30   ` H. J. Lu
2006-07-17 22:53     ` H. J. Lu
2006-07-18  3:04     ` Alan Modra
2006-07-18 16:28       ` Paul R. Nash
2006-07-18 17:20         ` Andreas Schwab
2006-07-19  1:54       ` Alan Modra
2006-07-19  3:44         ` Paul R. Nash
2006-07-19  4:23           ` Alan Modra
2006-07-19 16:33             ` Paul R. Nash
2006-07-18 16:08   ` Paul R. Nash

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=20060717020350.GH18571@bubble.grove.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sourceware.org \
    --cc=nashpaulr@gmail.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).