Re: [PATCH] objdump: Fix private header ('-p') import table output for pe-aarch64
Project / Subsystem
binutils / objdump
Date
2026-06-30
Proposer
Jon Turney <jon.turney@dronecode.org.uk>
Source type
public_inbox
Consensus
Proposed
Sentiment
9/10
Technical tradeoffs
- • Improves accuracy of `objdump` output for 64-bit PE files.
- • Addresses a bug that could lead to incomplete analysis of executable dependencies.
All attributes
- project
- binutils
- subsystem
- objdump
- patch_id
- —
- discussion_id
- 20260619134339.73604-1-jon.turney@dronecode.org.uk
- source_type
- public_inbox
- title
- Re: [PATCH] objdump: Fix private header ('-p') import table output for pe-aarch64
- headline
- objdump: Fix private header ('-p') import table output for pe-aarch64
- tldr
- Corrects truncation of import table output for PE32+ (64-bit) executables, particularly on AArch64.
- proposer
- Jon Turney <jon.turney@dronecode.org.uk>
- consensus
- Proposed
- outcome
- ready
- sentiment_score
- 9
- technical_tradeoffs
-
- • Improves accuracy of `objdump` output for 64-bit PE files.
- • Addresses a bug that could lead to incomplete analysis of executable dependencies.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • objdump
- • pe/coff
- • windows
- • aarch64
- • bugfix
- bugzilla_url
- —
- date
- 2026-06-30T00:00:00.000Z
Re: [PATCH] objdump: Fix private header ('-p') import table output for pe-aarch64
This patch fixes an issue where the import table output for PE32+ (64-bit) executables, processed with objdump -p, was truncated after the first import on AArch64 and potentially other 64-bit architectures. The fix correctly distinguishes between PE32 (32-bit) and PE32+ (64-bit) formats based on the PE specification, ensuring that 64-bit import lookup table entries are handled appropriately.