From: Jeffrey Walton <noloader@gmail.com>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: Best reference for understanding ELF format
Date: Tue, 20 Apr 2021 04:14:19 -0400 [thread overview]
Message-ID: <CAH8yC8mPgUsmZ=11H1v6ZzM9wAbVt3ZSR-FSnRKUDV-vEUD=JA@mail.gmail.com> (raw)
In-Reply-To: <CABrM6w=+4UVf0h7ZyOPBE6rxEMoL5+eLrm6Nu7whPGPZhho+jw@mail.gmail.com>
On Sat, Apr 17, 2021 at 9:15 AM Peng Yu via Libc-help
<libc-help@sourceware.org> wrote:
>
> That is a book. By definition, a book will not be complete since a
> book is not written for completeness?
>
> For the best reference (as "reference" may have muliple meanings maybe
> I should use the word "spec" to avoid ambiguity), I found the
> following two documents. One is for 32-bit, the other is for 64-bit.
> Are they the most current ones? Other there any other documents that
> cover the things missed by them?
For a spec, see Dreeper's DSO HowTo at
https://www.akkadia.org/drepper/dsohowto.pdf.
Jeff
prev parent reply other threads:[~2021-04-20 8:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 3:38 Peng Yu
2021-04-16 3:47 ` Mike Frysinger
2021-04-17 12:31 ` Peng Yu
2021-04-19 7:29 ` Szabolcs Nagy
2021-04-19 7:53 ` Florian Weimer
2021-04-20 1:58 ` Peng Yu
2021-04-20 7:08 ` tomas
2021-04-20 13:19 ` Mike Frysinger
2021-04-20 13:40 ` Peng Yu
2021-04-20 14:18 ` Mike Frysinger
2021-04-20 15:12 ` Peng Yu
2021-04-20 16:39 ` Jeffrey Walton
2021-04-20 16:51 ` Carlos O'Donell
2021-04-21 3:19 ` Peng Yu
2021-04-20 17:55 ` Mike Frysinger
2021-04-20 18:01 ` Mike Frysinger
2021-04-20 8:14 ` Jeffrey Walton [this message]
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='CAH8yC8mPgUsmZ=11H1v6ZzM9wAbVt3ZSR-FSnRKUDV-vEUD=JA@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=libc-help@sourceware.org \
--cc=pengyu.ut@gmail.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).