From: hjl@lucon.org (H.J. Lu)
To: chris@beezer.med.miami.edu (Christopher C Chimelis)
Cc: bfd@cygnus.com, ian@cygnus.com (Ian Lance Taylor)
Subject: A patch for elf.c
Date: Tue, 08 Dec 1998 09:57:00 -0000 [thread overview]
Message-ID: <m0znRNv-00038dC@ocean.lucon.org> (raw)
In-Reply-To: <Pine.LNX.3.96.981208082500.26204A-100000@beezer.med.miami.edu>
>
>
> On Mon, 7 Dec 1998, H.J. Lu wrote:
>
> > Could you please tell me on which platform you had this problem?
>
> Alpha running Debian Linux.
Thanks for this information. BTW, have you mentioned this in your first
bug report? I think this patch fixes the bug.
Ian, this bug happens on ELF/Alpha when you strip more than one shared
libraries at a time. It is not the first bfd_zalloc/bfd_alloc bug in
bfd. It is quite annoying.
--
H.J. Lu (hjl@gnu.org)
----
Tue Dec 8 07:51:09 1998 H.J. Lu (hjl@gnu.org)
* elf.c (copy_private_bfd_data): Use bfd_zalloc instead of
bfd_alloc.
Index: elf.c
===================================================================
RCS file: /home/work/cvs/gnu/binutils/bfd/elf.c,v
retrieving revision 1.40
diff -u -p -r1.40 elf.c
--- elf.c 1998/12/05 03:38:53 1.40
+++ elf.c 1998/12/08 17:48:01
@@ -3317,7 +3317,7 @@ copy_private_bfd_data (ibfd, obfd)
/* Allocate a segment map big enough to contain all of the
sections we have selected. */
m = ((struct elf_segment_map *)
- bfd_alloc (obfd,
+ bfd_zalloc (obfd,
(sizeof (struct elf_segment_map)
+ ((size_t) csecs - 1) * sizeof (asection *))));
if (m == NULL)
next parent reply other threads:[~1998-12-08 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.981208082500.26204A-100000@beezer.med.miami.edu>
1998-12-08 9:57 ` H.J. Lu [this message]
1998-12-08 10:28 ` Christopher C Chimelis
1998-12-08 11:26 ` Ian Lance Taylor
1998-12-08 11:34 ` Christopher C Chimelis
1998-12-09 7:42 ` H.J. Lu
1998-12-09 8:04 ` Roland McGrath
1998-12-09 9:35 ` Ian Lance Taylor
1998-12-09 10:03 ` Jeffrey A Law
1998-12-09 16:27 ` Stan Shebs
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=m0znRNv-00038dC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=bfd@cygnus.com \
--cc=chris@beezer.med.miami.edu \
--cc=ian@cygnus.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).