From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tom@tromey.com>,
Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Resolve dynamic types before computing pointer size
Date: Wed, 20 Oct 2021 12:29:22 -0700 [thread overview]
Message-ID: <fe47b785-0be6-d55f-f825-14144a727e43@redhat.com> (raw)
In-Reply-To: <874k9dx9xf.fsf@tromey.com>
On 10/19/21 09:21, Tom Tromey wrote:
>>>>>> "Keith" == Keith Seitz via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Keith> This patch addresses this by changing the API for find_size_for_pointer
> Keith> so that it takes the actual struct value of the pointer variable,
> Keith> resolves the pointer's target type if it is dynamic, and returns
> Keith> a size based on this resolved type.
>
> Thanks, this looks good to me.
Unfortunately, my patch to find_size_for_pointer_math interferes with your recently committed
patch ["Fix bug in dynamic type resolution"], which you "snuck" [:-)] in before I could finish
rebasing and retesting my patch.
With my patch applied:
+FAIL: gdb.ada/array_of_variant.exp: scenario=minimal: print first element of another_array
+FAIL: gdb.ada/array_of_variant.exp: scenario=minimal: print second element of another_array
In both cases, we see "Cannot access memory at address 0x4".
So until I figure this out, I'll have to put this patch into a holding pattern.
Thank you for the review!
Keith
next prev parent reply other threads:[~2021-10-20 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 16:42 Keith Seitz
2021-10-19 16:21 ` Tom Tromey
2021-10-20 19:29 ` Keith Seitz [this message]
2021-10-20 21:42 ` Tom Tromey
2021-10-21 18:19 ` Tom Tromey
2021-11-11 18:21 ` Keith Seitz
2022-02-24 19:51 ` Keith Seitz
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=fe47b785-0be6-d55f-f825-14144a727e43@redhat.com \
--to=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).