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?


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

As someone else asked: that explains why it is not readonly when -fPIC
is provided.  But why isn't it readonly if -fPIC is not provided?  After
all, in that same situation the text section is readonly even though it
contains relocations.




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