RE: How to access an applications ELF program header and ELF section header at runtime

["Bharath Ramesh" <bramesh at vt dot edu>]

> -----Original Message-----
> From: patofiero@gmail.com [mailto:patofiero@gmail.com] On Behalf Of
> Carlos O'Donell
> Sent: Wednesday, August 19, 2009 8:39 AM
> To: Bharath Ramesh
> Cc: Eduardo; libc-help@sourceware.org
> Subject: Re: How to access an applications ELF program header and ELF
> section header at runtime
> 
> On Wed, Aug 19, 2009 at 12:37 AM, Bharath Ramesh<bramesh@vt.edu> wrote:
> > Thanks for the reply, are these symbols __data_start, __bss_start
> specific
> > to Linux or would they work under any GNU system running a different
> kernel.
> > I am trying to keep my work portable to any system that uses GNU
> libc, but
> > not particularly the Linux kernel.
> 
> There is no guarantee that these symbols exist, or that they will
> remain the same in the next release.
> 
> In practice they are part of the standard Linux application linker
> script, which uses the symbol to mark the start and end of .data and
> .bss.
> 
> The .data and .bss sections are also not guaranteed to exist, and we
> now support read-only data in the form of the .rodata section.

Given this premise that these symbols are part of the linker script and the
fact that the existence of .data and .bss section is not guaranteed, is
there a consistent way of locating the region/section where all the global
data of an application is stored in the applications address space and the
length of this region/section.

> 
> Good luck with your project.
> 

Thank you, appreciate that.


Regards,

Bharath

Attachment: smime.p7s
Description: S/MIME cryptographic signature