This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: name collision for ELF reloc sections
- To: Nick Clifton <nickc@cygnus.com>
- Subject: Re: name collision for ELF reloc sections
- From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>
- Date: 11 May 1999 15:52:09 +0200
- Cc: binutils@sourceware.cygnus.com
- References: <199905111317.GAA15498@elmo.cygnus.com>
Nick Clifton <nickc@cygnus.com> writes:
|> 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 think the convention only holds for predefined sections, but not for
user defined sections.
Andreas.
--
Andreas Schwab "And now for something
schwab@issan.cs.uni-dortmund.de completely different"
schwab@gnu.org