From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 309 invoked by alias); 7 May 2006 21:32:34 -0000 Received: (qmail 300 invoked by uid 22791); 7 May 2006 21:32:33 -0000 X-Spam-Check-By: sourceware.org Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.184) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 07 May 2006 21:32:31 +0000 Received: by nf-out-0910.google.com with SMTP id l24so801193nfc for ; Sun, 07 May 2006 14:32:28 -0700 (PDT) Received: by 10.49.92.2 with SMTP id u2mr676913nfl; Sun, 07 May 2006 14:32:28 -0700 (PDT) Received: by 10.49.28.11 with HTTP; Sun, 7 May 2006 14:32:28 -0700 (PDT) Message-ID: <22080b0a0605071432v33c7d34eoba42611e84804db6@mail.gmail.com> Date: Mon, 08 May 2006 06:43:00 -0000 From: "Ravi Ramaseshan" To: "Torsten Mohr" Subject: Re: sections, overview of their meaning? Cc: "Nick Clifton" , binutils@sourceware.org In-Reply-To: <200605072318.56832.tmohr@s.netic.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200605061326.26393.tmohr@s.netic.de> <445E0F2E.2000509@redhat.com> <200605072318.56832.tmohr@s.netic.de> X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00141.txt.bz2 Hi, On 5/7/06, Torsten Mohr 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? 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. Cheers, -- Ravi Ramaseshan http://www.geocities.com/ramaseshan_ravi/ " Reality is only something we believe in strongly. "