Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Muhammad Kamran <Muhammad.Kamran@arm.com>,
	Florian Weimer <fweimer@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Andrew Burgess <aburgess@redhat.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>
Subject: Re: [PATCH v2 1/1] gdb: Preserve IFUNC marker when finding inferior functions
Date: Tue, 30 Jun 2026 15:29:20 +0000	[thread overview]
Message-ID: <PAWPR08MB898210E978D642ED2103DF9583F72@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <549b8d25-1102-42bc-96d0-24ac30060ea0@arm.com>

Hi Muhammad,

> Yes.  GDB should prefer the cache/GOT path and avoid resolver calls
> where possible.  The patch does not make resolver calls safer or add a
> new resolver-calling mechanism; it just preserves the IFUNC marker so
> the existing IFUNC resolution path is used instead of calling the
> resolver address as though it were malloc itself.

Indeed - while the patch works for now as a workaround, directly calling
ifunc resolvers without following the ifunc ABI does not work. GDB only
passes HWCAP as the first argument, so the resolver may return different
functions due to the set of HWCAP values given not being identical between
GDB and GLIBC (ie. It could call the wrong malloc implementation that was
not selected or initialized).

So the best option is to call dlsym() as Florian suggested.

Cheers,
Wilco

  reply	other threads:[~2026-06-30 15:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 15:20 [PATCH v2 0/1] " Muhammad Kamran
2026-06-25 15:20 ` [PATCH v2 1/1] " Muhammad Kamran
2026-06-25 20:05   ` Simon Marchi
2026-06-26  9:24     ` Muhammad Kamran
2026-06-26 14:20       ` Simon Marchi
2026-06-29 15:43         ` Muhammad Kamran
2026-06-29 21:11   ` Florian Weimer
2026-06-30  9:13     ` Yury Khrustalev
2026-06-30  9:18     ` Yury Khrustalev
2026-06-30  9:42       ` Wilco Dijkstra
2026-06-30 11:53         ` Florian Weimer
2026-07-21 17:10           ` Tom Tromey
2026-07-21 19:45             ` Florian Weimer
2026-07-22 13:36               ` Tom Tromey
2026-06-30 14:15     ` Muhammad Kamran
2026-06-30 15:29       ` Wilco Dijkstra [this message]
2026-07-03 12:56         ` Simon Marchi
2026-07-07 12:15           ` Muhammad Kamran

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=PAWPR08MB898210E978D642ED2103DF9583F72@PAWPR08MB8982.eurprd08.prod.outlook.com \
    --to=wilco.dijkstra@arm.com \
    --cc=Muhammad.Kamran@arm.com \
    --cc=Yury.Khrustalev@arm.com \
    --cc=aburgess@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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