This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Defining a section that isn't file-backed

From: Mike Hearn <mike at theoretic dot com>
To: Ian Lance Taylor <ian at wasabisystems dot com>
Cc: Nick Clifton <nickc at redhat dot com>, binutils at sources dot redhat dot com
Date: Thu, 26 Feb 2004 14:13:41 +0000
Subject: Re: Defining a section that isn't file-backed
References: <pan.2004.02.22.18.50.58.299730@theoretic.com> <m3brnq9lcf.fsf@redhat.com> <1077545399.3053.8.camel@linux.littlegreen> <m3smh195zk.fsf@redhat.com> <1077753253.4190.13.camel@linux.littlegreen> <m3r7wibs6c.fsf@gossamer.airs.com>

On Thu, 2004-02-26 at 00:28, Ian Lance Taylor wrote:
> ELF sections created using the assembler .section pseudo-op are
> read-only by default.  They only acquire the write flag if you specify
> it explicitly.

Does the "a" flag include write as well? If not then I'm not sure why
the section is being mmapped rwx - are there other factors that can
influence this?

thanks -mike

Follow-Ups:
- Re: Defining a section that isn't file-backed
  - From: Ian Lance Taylor

References:
- Defining a section that isn't file-backed
  - From: Mike Hearn
- Re: Defining a section that isn't file-backed
  - From: Nick Clifton
- Re: Defining a section that isn't file-backed
  - From: Mike Hearn
- Re: Defining a section that isn't file-backed
  - From: Nick Clifton
- Re: Defining a section that isn't file-backed
  - From: Mike Hearn
- Re: Defining a section that isn't file-backed
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]