All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 218018] dl_iterate_phdr should mention Elf64_Phdr (in addition to Elf32_Phdr).
Date: Wed, 27 Dec 2023 16:41:48 +0000	[thread overview]
Message-ID: <bug-218018-11311-djl3NOtVOy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218018-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218018

Rajesh (r.pandian@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r.pandian@gmail.com

--- Comment #1 from Rajesh (r.pandian@gmail.com) ---
(In reply to Paul Pluzhnikov from comment #0)
> dl_iterate_phdr should mention Elf64_Phdr (in addition to Elf32_Phdr).
> Currently the man page says:
> 
> These program headers are structures of the following form:
>   typedef { ... } Elf32_Phdr;
> 
> which is obviously wrong for 64-bit binaries.

Hello Paul,

Do you think the following would be helpful.

Replacing "These program headers are structures of the following form:" with
the following

The ELF program header is described by the type Elf32_Phdr or Elf64_Phdr
depending on the architecture. Following is an example of 32 bit architecture.
Refer to elf (man elf) for more information on 64 bit architecture.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2023-12-27 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 21:56 [Bug 218018] New: dl_iterate_phdr should mention Elf64_Phdr (in addition to Elf32_Phdr) bugzilla-daemon
2023-12-27 16:41 ` bugzilla-daemon [this message]
2023-12-27 16:47 ` [Bug 218018] " bugzilla-daemon
2024-01-01 11:53   ` Alejandro Colomar
2023-12-28 16:01 ` bugzilla-daemon
2024-01-01 11:53 ` bugzilla-daemon

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=bug-218018-11311-djl3NOtVOy@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.