From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26762 invoked by alias); 7 May 2006 23:05:43 -0000 Received: (qmail 26754 invoked by uid 22791); 7 May 2006 23:05:43 -0000 X-Spam-Check-By: sourceware.org Received: from mail.s.netic.de (HELO mail.s.netic.de) (212.9.160.11) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 07 May 2006 23:05:41 +0000 Received: from host-213-178-187-12.dsl.netic.de ([213.178.187.12] helo=schleim.qwe.de) by mail.s.netic.de with esmtp (Exim 4.51) id 1FcsJn-000EKL-Bq; Mon, 08 May 2006 01:05:39 +0200 Received: from localhost (localhost [IPv6:::1]) by schleim.qwe.de (Postfix) with ESMTP id 690DE3A73F; Mon, 8 May 2006 01:07:40 +0200 (CEST) From: Torsten Mohr To: "Ravi Ramaseshan" Subject: Re: sections, overview of their meaning? Date: Mon, 08 May 2006 15:58:00 -0000 User-Agent: KMail/1.8 Cc: binutils@sourceware.org References: <200605061326.26393.tmohr@s.netic.de> <200605072318.56832.tmohr@s.netic.de> <22080b0a0605071432v33c7d34eoba42611e84804db6@mail.gmail.com> In-Reply-To: <22080b0a0605071432v33c7d34eoba42611e84804db6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605080107.40079.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/msg00143.txt.bz2 Hi, thanks for these informations, it helped for .comment, .rel* and other common parts. Thanks, Torsten. > 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. "