public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: gatgul@voicenet.com (Uncle George)
Cc: egcs@cygnus.com
Subject: Re: Dynamic Linkage Problem
Date: Sat, 19 Sep 1998 16:10:00 -0000	[thread overview]
Message-ID: <m0zKSx3-00038xC@ocean.lucon.org> (raw)
In-Reply-To: <3603CE50.20257C9C@voicenet.com>

> 
> This is a multi-part message in MIME format.
> --------------BE666905CE35FAB88D17BE66
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> while ur at it
>     can u ( if u havent allready ) fix a LD bug related to the alpha. the
> .dynsym section should be cleared out on the alpha before use. Some entries
> in the  table are not cleared when the table becomes populated, and random
> numbers are left within the table. An example would be the libdl.so
> distributed with the 6cd jewel set. It has bogus entries that causes gdb to
> go core.
> I had posted this patch before, but dont know what happened to it - if
> anything.
> 

From bfd/ChangeLog.linux in binutils 2.9.1.0.13:

Sun Aug  9 11:52:47 1998  H.J. Lu  (hjl@gnu.org)
       
        * elf32-arm.c (elf_arm_size_dynamic_sections): Use bfd_zalloc
        instead of bfd_alloc for allocating the section contents.
        * elf32-i386.c (elf_i386_size_dynamic_sections): Likewise.
        * elf32-m68k.c (elf_m68k_size_dynamic_sections): Likewise.
        * elf32-mips.c (mips_elf_size_dynamic_sections): Likewise.
        * elf32-sparc.c (elf32_sparc_size_dynamic_sections): Likewise.
        * elf64-alpha.c (elf64_alpha_do_reloc_gpdisp): Likewise.
        * elf64-mips.c (mips_elf64_write_relocs): Likewise.
        * elfcode.h (write_relocs): Likewise.
        * elflink.h (NAME(bfd_elf,size_dynamic_sections)): Likewise.
        (NAME(bfd_elf,size_dynamic_sections)): Likewise.
        (NAME(bfd_elf,size_dynamic_sections)): Likewise.
        (elf_bfd_final_link): Likewise.

Is that good enough for you?


H.J.

  reply	other threads:[~1998-09-19 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-18  9:44 Bret Orsburn
1998-09-18 14:46 ` H.J. Lu
1998-09-22  9:45   ` Bret Orsburn
1998-09-18 21:46 ` Richard Henderson
1998-09-19  8:24   ` Uncle George
1998-09-19 16:10     ` H.J. Lu [this message]
1998-09-19 16:10     ` Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
1998-09-15 20:44 Bret Orsburn

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=m0zKSx3-00038xC@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=egcs@cygnus.com \
    --cc=gatgul@voicenet.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).