From: Alan Modra <amodra@bigpond.net.au>
To: Jakub Jelinek <jakub@redhat.com>
Cc: binutils@sources.redhat.com, hpa@zytor.com
Subject: Re: [PATCH] Avoid ld segfaults on nasm objects
Date: Fri, 10 Dec 2004 04:42:00 -0000 [thread overview]
Message-ID: <20041210044158.GB11634@bubble.modra.org> (raw)
In-Reply-To: <20041209142940.GG5149@sunsite.mff.cuni.cz>
On Thu, Dec 09, 2004 at 03:29:40PM +0100, Jakub Jelinek wrote:
> BTW: I'm not sure what exactly is ld doing when number of sections
> is bigger than 65536, particularly I don't see anything that would
> remap internal symbol's st_shndx SHN_LORESERVE..SHN_HIRESERVE range
Well, no, any internal symbol in that range won't be mapped. However,
ld won't create normal elf sections that use these reserved indices, so
the values set for st_shndx, eg. in elf_link_output_extsym from
_bfd_elf_section_from_bfd_section, won't be in that range.
> * elf.c (bfd_elf_local_sym_name): Avoid crashes with invalid
> st_shndx on STT_SECTION sections.
OK.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
prev parent reply other threads:[~2004-12-10 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 14:29 Jakub Jelinek
2004-12-10 4:42 ` Alan Modra [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=20041210044158.GB11634@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=hpa@zytor.com \
--cc=jakub@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).