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: Ian Lance Taylor <ian at wasabisystems dot com>
To: Mike Hearn <mike at theoretic dot com>
Cc: Nick Clifton <nickc at redhat dot com>, binutils at sources dot redhat dot com
Date: 25 Feb 2004 19:28:11 -0500
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>

Mike Hearn <mike@theoretic.com> writes:

> I've read the gas manual and it looks like the only section flags in ELF
> binaries do not allow you to mark a section as being mapped readonly.
> Please tell me this isn't the case! I'm sure it must be wrong, as there
> are sections that are clearly being mmaped with (PROT_READ), I just
> can't see how it's done.

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.

Ian

Follow-Ups:
- Re: Defining a section that isn't file-backed
  - From: Mike Hearn

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

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