This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: why isn't the .eh_frame section marked READONLY?
- To: Jason Merrill <jason at cygnus dot com>
- Subject: Re: why isn't the .eh_frame section marked READONLY?
- From: Andreas Schwab <schwab at issan dot informatik dot uni-dortmund dot de>
- Date: 02 Jun 1998 13:36:21 +0200
- Cc: jbuck at synopsys dot com (Joe Buck), egcs at cygnus dot com
- References: <199806020107.SAA21580.cygnus.egcs@atrus.synopsys.com> <u9btscdsob.fsf@yorick.cygnus.com>
Jason Merrill <jason@cygnus.com> writes:
|> >>>>> Joe Buck <jbuck@synopsys.com> writes:
|>
|> > Some folks in comp.os.linux.development.system are asking why
|> > the .eh_frame section isn't readonly. It's never changed at
|> > runtime, is it? Is there some other reason it must be writable?
|>
|> Because it has relocations, so the dynamic loader needs to fix it up.
But this is only relevant in PIC. For non-PIC the section can be
readonly.
--
Andreas Schwab "And now for something
schwab@issan.informatik.uni-dortmund.de completely different"
schwab@gnu.org