public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Binutils Development <binutils@sourceware.org>,
	Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH 3/5] remove deleted BFDs from the archive cache
Date: Fri, 17 Aug 2012 00:48:00 -0000	[thread overview]
Message-ID: <CAMe9rOp7WhXAWdy=vT-HWPrV8aW+WOz4pzd9RyZDyW-ue-K+qw@mail.gmail.com> (raw)
In-Reply-To: <87wr0zsw9h.fsf@fleche.redhat.com>

On Wed, Aug 15, 2012 at 2:03 PM, Tom Tromey <tromey@redhat.com> wrote:
> HJ> It breaks strip:
> HJ> http://sourceware.org/bugzilla/show_bug.cgi?id=14475
>
> Thanks
>
> Here is a patch to fix the problem.
>
> The bug is that bfd_ar_hdr_from_filesystem creates the areltdata on the
> archive's objalloc.  But, since this data is attached to the member BFD,
> it should really be created on the member's objalloc.
>
> This also fixes another bug I noticed in bfd_ar_hdr_from_filesystem.
> This code tries to free 'ared' in one case -- but that is wrong, as this
> is not allocated using malloc.
>
> I could see the bug before this patch using valgrind or -lmcheck.  After
> the patch the problem is gone.
>
> Ok?
>
> Tom
>
> 2012-08-15  Tom Tromey  <tromey@redhat.com>
>
>         PR binutils/14475:
>         * archive.c (bfd_ar_hdr_from_filesystem): Allocate areltdata on
>         'member' BFD.  Don't try to free 'ared'.
>
> Index: archive.c
> ===================================================================
> RCS file: /cvs/src/src/bfd/archive.c,v
> retrieving revision 1.89
> diff -u -r1.89 archive.c
> --- archive.c   9 Aug 2012 06:25:52 -0000       1.89
> +++ archive.c   15 Aug 2012 21:01:51 -0000
> @@ -1896,7 +1896,7 @@
>      }
>
>    amt = sizeof (struct ar_hdr) + sizeof (struct areltdata);
> -  ared = (struct areltdata *) bfd_zalloc (abfd, amt);
> +  ared = (struct areltdata *) bfd_zalloc (member, amt);
>    if (ared == NULL)
>      return NULL;
>    hdr = (struct ar_hdr *) (((char *) ared) + sizeof (struct areltdata));
> @@ -1927,10 +1927,7 @@
>    _bfd_ar_spacepad (hdr->ar_mode, sizeof (hdr->ar_mode), "%-8lo",
>                     status.st_mode);
>    if (!_bfd_ar_sizepad (hdr->ar_size, sizeof (hdr->ar_size), status.st_size))
> -    {
> -      free (ared);
> -      return NULL;
> -    }
> +    return NULL;
>    memcpy (hdr->ar_fmag, ARFMAG, 2);
>    ared->parsed_size = status.st_size;
>    ared->arch_header = (char *) hdr;

I am not sure if it is correct to use the member's objalloc since
areltdata may be allocated from _bfd_generic_read_ar_hdr_mag
which takes archive bfd.

-- 
H.J.

      parent reply	other threads:[~2012-08-16 21:35 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 14:55 Tom Tromey
2012-08-03 16:12 ` Alan Modra
2012-08-03 20:56   ` Tom Tromey
2012-08-08 22:47   ` Tom Tromey
2012-08-09 10:35     ` Alan Modra
2012-08-15 20:14       ` H.J. Lu
2012-08-15 21:30         ` Tom Tromey
2012-08-16 14:47           ` Alan Modra
2012-08-16 16:31             ` H.J. Lu
2012-08-16 18:14               ` Tom Tromey
2012-08-16 18:33                 ` H.J. Lu
2012-08-16 18:45                   ` Tom Tromey
2012-08-16 18:49                     ` H.J. Lu
2012-08-16 18:55                       ` Tom Tromey
2012-08-16 20:33                         ` Tom Tromey
2012-08-16 20:38                         ` H.J. Lu
2012-08-16 21:11                 ` H.J. Lu
2012-08-16 21:35                 ` H.J. Lu
2012-08-17  1:01                 ` Alan Modra
2012-08-17  1:06                   ` H.J. Lu
2012-08-17  2:44                     ` Alan Modra
2012-08-17  4:56                       ` Hans-Peter Nilsson
2012-08-17  5:04                         ` Alan Modra
2012-08-17  5:08                         ` H.J. Lu
2012-08-17  5:30                           ` H.J. Lu
2012-08-17  5:42                             ` H.J. Lu
2012-08-17  5:45                               ` H.J. Lu
2012-08-17  6:01                                 ` H.J. Lu
2012-08-17 13:10                                   ` H.J. Lu
2012-08-17 16:50                                     ` Hans-Peter Nilsson
2012-08-17 16:01                           ` Hans-Peter Nilsson
2012-08-17 16:10                             ` H.J. Lu
2012-08-17 16:14                               ` Hans-Peter Nilsson
2012-08-17 16:13                       ` Tom Tromey
2012-08-17 16:26                         ` H.J. Lu
2012-08-17 16:51                           ` Tom Tromey
2012-08-17 17:11                             ` H.J. Lu
2012-08-17 17:22                               ` Tom Tromey
2012-08-17 17:22                                 ` H.J. Lu
2012-08-17 19:03                                   ` Tom Tromey
2012-08-17 19:13                                     ` H.J. Lu
2012-08-18  4:37                         ` Alan Modra
2012-08-21  9:55                           ` Tom Tromey
2012-08-17  1:17                   ` Alan Modra
2012-08-17 15:36                   ` Tom Tromey
2012-08-17 15:38                     ` H.J. Lu
2012-08-17 15:43                       ` Tom Tromey
2012-08-17  0:48           ` H.J. Lu [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='CAMe9rOp7WhXAWdy=vT-HWPrV8aW+WOz4pzd9RyZDyW-ue-K+qw@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=tromey@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).