From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: Nick Clifton <nickc@redhat.com>
Cc: eagle_zhou@ali.com.tw, binutils@sources.redhat.com
Subject: Re: the question about PT_DYNAMIC's p_offset value in elf file for mips platform
Date: Tue, 26 Oct 2004 13:18:00 -0000 [thread overview]
Message-ID: <20041026131820.GE24545@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <417E295F.9030006@redhat.com>
Nick Clifton wrote:
> Hi Eagle,
>
> >I think that .dynamic section should be the first section of dynamic
> >segment.
>
> For most ports this is true. But for the MIPS it is not. I will let a
> MIPS expert explain why, as I do not actually know the reason.
I guess it is for historic reasons and/or compatibility to other
(read IRIX) operating systems.
> >If .dynamic section is not the first section in dynamic segment,
> >how can i get other dynamic section information?
>
> If you have a section header then discovering this information is
> simple. Otherwise there is no easy way. I think that with MIPS ports
> which do not have the .dynamic section at the start of the PT_DYNAMIC
> segment there is a requirement to keep the section header in an
> executable. (I expect someone will correct me on this).
Glibc's ld.so finds the offset from the magic _DYNAMIC symbol.
Thiemo
next prev parent reply other threads:[~2004-10-26 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 9:10 eagle_zhou
2004-10-26 10:33 ` Nick Clifton
2004-10-26 13:18 ` Thiemo Seufer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-26 7:21 eagle_zhou
2004-10-26 8:24 ` Nick Clifton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041026131820.GE24545@rembrandt.csv.ica.uni-stuttgart.de \
--to=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=binutils@sources.redhat.com \
--cc=eagle_zhou@ali.com.tw \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).