This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: sections, overview of their meaning?
Hi,
thanks for these informations, it helped for .comment, .rel*
and other common parts.
Thanks,
Torsten.
> Hi,
>
> On 5/7/06, Torsten Mohr <tmohr@s.netic.de> wrote:
> > Basically, i'd like to ask for nearly all sections in the
> > original V850 linker script, except the obvious ones like
> > .text, .data, .bss, ... . What is ".dynamic" doing, what
> > are all the .rel* and .rela* for?
>
> The following document should give you the description of some of the
> common sections including the .dynamic, .rel, .rela and others :
> http://www.skyfree.org/linux/references/ELF_Format.pdf
>
> > What about .ctors and .dtors? They sound like C++ constructors
> > and destructors, but do they contain code (ROM) or data (RAM)
> > used in the constructors?
>
> <quote: http://www.delorie.com/gnu/docs/gcc/gccint_149.html >
> The best way to handle static constructors works only for object file
> formats which provide arbitrarily-named sections. A section is set
> aside for a list of constructors, and another for a list of
> destructors. Traditionally these are called `.ctors' and `.dtors'.
> Each object file that defines an initialization function also puts a
> word in the constructor section to point to that function. The linker
> accumulates all these words into one contiguous `.ctors' section.
> Termination functions are handled similarly.
> </quote>
>
> Cheers,
> --
> Ravi Ramaseshan
> http://www.geocities.com/ramaseshan_ravi/
>
> " Reality is only something we believe in strongly. "