From: Yury Khrustalev <yury.khrustalev@arm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Muhammad Kamran <muhammad.kamran@arm.com>,
<gdb-patches@sourceware.org>,
Andrew Burgess <aburgess@redhat.com>,
Wilco Dijkstra <Wilco.Dijkstra@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 10:13:15 +0100 [thread overview]
Message-ID: <akOIq1OSPLrujmAv@arm.com> (raw)
In-Reply-To: <lhuh5ml6oic.fsf@oldenburg.str.redhat.com>
* Florian
On Mon, Jun 29, 2026 at 11:11:07PM +0200, Florian Weimer wrote:
> * Muhammad Kamran:
>
> > GDB calls find_function_in_inferior ("malloc") when expression
> > evaluation needs to allocate memory in the inferior, e.g. for string
> > literal arguments.
>
> So this looks fairly nasty. This looks fairly harmless as far as GDB
> expressions go:
>
> > + gdb_test "print (get_string (\"hello-ifunc\"), str_in_arena ())" \
>
> We can actually detect the GDB call and glibc and do the right thing:
>
> [PATCH 0/2] Work around GDB bug overwriting __libc_malloc
> <https://inbox.sourceware.org/libc-alpha/cover.1782766548.git.fweimer@redhat.com/>
There is another work-around that is already present: Glibc can be
configured with --disable-multi-arch and this will disable all ifuncs
including malloc ones. Sorry, I forgot about it earlier. This might not
be ideal if you intend to debug these ifuncs in Glibc, but it's probably
the best way for a broken GDB.
Thanks,
Yury
next prev parent reply other threads:[~2026-06-30 9:15 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 [this message]
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
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=akOIq1OSPLrujmAv@arm.com \
--to=yury.khrustalev@arm.com \
--cc=Wilco.Dijkstra@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=muhammad.kamran@arm.com \
--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