Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: JIELUN WU <firmiana402@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Check DW_OP_deref_type size against type
Date: Sat, 22 Aug 2026 10:22:04 +0800	[thread overview]
Message-ID: <cedff627-924b-4a8b-bd15-e3ea1e39fc23@gmail.com> (raw)
In-Reply-To: <87pkzbnul3.fsf@tromey.com>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]


On 2026/8/22 3:26, Tom Tromey wrote:
>>>>>> 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


Hi Tom,

Thanks for checking. I believe my copyright assignment has already been
completed and should be on file. I started the process in late June and
received the final confirmation email in early August.

Please let me know if it is not showing up in the records, or if you need
any additional information from me.

Best,
Jielun

[-- Attachment #2: Type: text/html, Size: 2566 bytes --]

      reply	other threads:[~2026-08-22  2:22 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
2026-08-22  2:22   ` JIELUN WU [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=cedff627-924b-4a8b-bd15-e3ea1e39fc23@gmail.com \
    --to=firmiana402@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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