This is the mail archive of the
mailing list for the GCC project.
Re: function addresses and ld.so
- From: David Mosberger <davidm at napali dot hpl dot hp dot com>
- To: Camm Maguire <camm at enhanced dot com>
- Cc: gcl-devel at gnu dot org, debian-ia64 at lists dot debian dot org, gcc at gcc dot gnu dot org,204789 at bugs dot debian dot org
- Date: Wed, 13 Aug 2003 16:35:36 -0700
- Subject: Re: function addresses and ld.so
- References: <E19mhZPfirstname.lastname@example.org>
- Reply-to: davidm at hpl dot hp dot com
>>>>> On Tue, 12 Aug 2003 18:24:47 -0400, Camm Maguire <email@example.com> said:
Camm> GCL stores addresses of its functions in data structures
Camm> allocated in the normal way in its .data section. It then
Camm> runs an unexec routine which saves the memory image including
Camm> these addresses to a file.
Isn't this a dangerous thing to do even on non-function-descriptor
architectures? If I understand you right, GCL depends on the loader
mapping the shared objects on subsequent executions at the exact same
location as during the original execution. Wouldn't, e.g.,
LD_PRELOADing something break this assumption?