From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schwab To: Nick Clifton Cc: binutils@sourceware.cygnus.com Subject: Re: name collision for ELF reloc sections Date: Thu, 01 Jul 1999 00:00:00 -0000 Message-id: References: <199905111317.GAA15498@elmo.cygnus.com> X-SW-Source: 1999-q2/msg00014.html Nick Clifton writes: |> Hi Andreas, |> |> : From: Andreas Schwab |> : |> : Nick Clifton 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