From: Muhammad Kamran <muhammad.kamran@arm.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Yury Khrustalev <Yury.Khrustalev@arm.com>,
Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Carlos O'Donell <carlos@redhat.com>,
Simon Marchi <simark@simark.ca>,
Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH v5 0/2] gdb: Fix internal inferior calls through GNU IFUNCs
Date: Mon, 17 Aug 2026 10:19:18 +0100 [thread overview]
Message-ID: <4ceccaac-8d04-4c13-8d73-2cd5c5643980@arm.com> (raw)
In-Reply-To: <20260816002317.2a44f116@f44-mesa-1>
On 16/08/2026 08:24, Kevin Buettner wrote:
> On Tue, 11 Aug 2026 13:12:17 +0000
> Muhammad Kamran <muhammad.kamran@arm.com> wrote:
>
>> This series fixes a GDB inferior-call issue exposed by malloc being a GNU
>> IFUNC in glibc on AArch64. The underlying problem is not AArch64-specific:
>> it can affect any inferior helper found through find_function_in_inferior's
>> minimal-symbol fallback when that helper is a GNU IFUNC.
>>
>> GDB calls find_function_in_inferior ("malloc") when expression evaluation
>> needs to allocate memory in the inferior, for example for string literal
>> arguments. In the minimal-symbol fallback, GDB created a synthetic ordinary
>> function pointer from the minimal symbol address. If the symbol was a GNU
>> IFUNC, this lost the IFUNC marker, so call_function_by_hand did not resolve
>> the symbol before calling it.
>>
>> Patch 1 checks the minimal symbol kind directly and propagates the GNU IFUNC
>> marker to the synthetic function type for mst_text_gnu_ifunc and
>> mst_data_gnu_ifunc symbols. The existing fallback address and return type
>> are unchanged.
>>
>> Patch 2 fixes the follow-on return-type issue after IFUNC resolution. When
>> the resolved target type, or the type inferred from the resolver return type,
>> does not provide a usable return type, find_function_addr now keeps the
>> original function type's return type. This preserves the synthetic fallback
>> return type used by find_function_in_inferior ("malloc").
>>
>> The tests add an internal inferior-call case using an IFUNC malloc and run it
>> through the existing gdb.base/gnu-ifunc.exp matrix for resolver attr,
>> resolver debug info, and resolved-target debug info.
>>
>> Changes since v4:
>> * Address feedback from Andrew Burgess <aburgess@redhat.com>.
>>
>> Changes since v3:
>> * Move the ifunc resolver into a shared library.
>>
>> Changes since v2:
>> * Rework the minimal-symbol fallback to check the minimal symbol kind
>> directly as suggested by Simon.
>> * Add coverage for both debug and no-debug IFUNC malloc variants by
>> using the existing framework.
>> * Preserve the original IFUNC return type when the resolved target type
>> is unknown.
>
> Andrew gave conditional approval for both parts in his v4 replies.
> I've looked over this v5 series; IMO, you've completely addressed his
> concerns. Therefore, I think you can consider this version approved;
> but do add Andrew's Approved-By tag. If you need a maintainer to push
> it for you, I'll be happy to do that.
Hi Kevin,
Thanks for reviewing.
I don't have write access, so I'd appreciate it if you could please push
the series for me.
Andrew gave his Approved-By on both patches, so please feel free to add:
Approved-By: Andrew Burgess <aburgess@redhat.com>
Thanks,
Kamran
>
> Reviewed-By: Kevin Buettner <kevinb@redhat.com>
>
next prev parent reply other threads:[~2026-08-17 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:12 Muhammad Kamran
2026-08-11 13:12 ` [PATCH v5 1/2] gdb: Preserve IFUNC marker when finding inferior functions Muhammad Kamran
2026-08-11 13:12 ` [PATCH v5 2/2] gdb: Keep original IFUNC return type when target type is unknown Muhammad Kamran
2026-08-16 7:24 ` [PATCH v5 0/2] gdb: Fix internal inferior calls through GNU IFUNCs Kevin Buettner
2026-08-17 9:19 ` Muhammad Kamran [this message]
2026-08-20 9:02 ` Yury Khrustalev
2026-08-20 11:55 ` Andrew Burgess
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=4ceccaac-8d04-4c13-8d73-2cd5c5643980@arm.com \
--to=muhammad.kamran@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=Yury.Khrustalev@arm.com \
--cc=aburgess@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simark@simark.ca \
--cc=thiago.bauermann@linaro.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