public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@cygnus.com>
To: binutils@sourceware.cygnus.com
Subject: Re: name collision for ELF reloc sections
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <199905111317.GAA15498@elmo.cygnus.com> (raw)

Hi Andreas,

: From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>
: 
: Nick Clifton <nickc@cygnus.com> writes:
: 
: |>   The patch solves this problem by making elf_fake_section look for
: |>   ".rel." as the start of a name of a REL section (and similarly
: |>   ".rela." for the start of a name of a RELA section).  Looking for
: |>   the extra period guarantees that the section name cannot have been
: |>   generated from a real C/C++ function name, but I do not know if this
: |>   is safe.  Is it possible to generate an ELF rel or rela section that
: |>   starts with .rel{a} but which does not have a second period
: |>   immediately following it ?
: 
: Yes.  Any relocation section that is associated with a section whose name
: does not start with a period will have such a name.
: 
: Andreas.

Darn.  OK - I know that the normal convention is to have all (ELF)
section names start with a period.  Does anyone know of any toolchains
which break this convention ?  (And which might have a reloc section
associated with such a section) ?

I have already commited my patch, so I would like to find out if I
have broken anything ... :-)

Cheers
	Nick

             reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Nick Clifton [this message]
1999-07-01  0:00 ` Andreas Schwab
1999-07-01  0:00 ` Ian Lance Taylor
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Ian Lance Taylor
1999-07-01  0:00 ` Andreas Schwab
1999-07-01  0:00 Nick Clifton

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=199905111317.GAA15498@elmo.cygnus.com \
    --to=nickc@cygnus.com \
    --cc=binutils@sourceware.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).