From: Tom Tromey <tom@tromey.com>
To: Jielun Wu <firmiana402@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Check DW_OP_deref_type size against type
Date: Fri, 21 Aug 2026 13:26:32 -0600 [thread overview]
Message-ID: <87pkzbnul3.fsf@tromey.com> (raw)
In-Reply-To: <20260814085303.2561156-1-firmiana402@gmail.com> (Jielun Wu's message of "Fri, 14 Aug 2026 16:53:03 +0800")
>>>>> Jielun Wu <firmiana402@gmail.com> writes:
> DWARF v5 requires the explicit size operand of DW_OP_deref_type to
> match the size of the referenced base type. The evaluator currently
> passes both sizes to dwarf_expr_context::deref without validating the
> encoding, and the generic dereference helper accepts the mismatch by
> zero-extending the bytes read from memory.
> Reject a mismatch after resolving the base type. Add a DWARF assembler
> test covering both DW_OP_deref_type and DW_OP_GNU_deref_type.
> Tested on x86_64-linux.
I think we're going to need copyright assignments in order to merge this
and the other patches.
You can email 'assign@gnu.org' to get started.
Tom
next prev parent reply other threads:[~2026-08-21 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 8:53 Jielun Wu
2026-08-14 19:44 ` Keith Seitz
2026-08-17 16:33 ` Simon Marchi
2026-08-21 19:26 ` Tom Tromey [this message]
2026-08-22 2:22 ` JIELUN WU
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=87pkzbnul3.fsf@tromey.com \
--to=tom@tromey.com \
--cc=firmiana402@gmail.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox