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: Andreas Schwab <schwab at issan dot informatik dot uni-dortmund dot de>
- Subject: Re: why isn't the .eh_frame section marked READONLY?
- From: Jason Merrill <jason at cygnus dot com>
- Date: 02 Jun 1998 11:37:07 -0700
- 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> <vyzd8csxcga.fsf@issan.informatik.uni-dortmund.de>
>>>>> Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> writes:
> 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.
Yes, but this is more hassle than it's worth. I'm not sure how linking PIC
with non-PIC code would work if that varied.
Jason