This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

Re: why isn't the .eh_frame section marked READONLY?


>>>>> 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


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