From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Yury Khrustalev <Yury.Khrustalev@arm.com>,
Florian Weimer <fweimer@redhat.com>
Cc: Muhammad Kamran <Muhammad.Kamran@arm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Andrew Burgess <aburgess@redhat.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 09:42:54 +0000 [thread overview]
Message-ID: <PAWPR08MB898253718529A2349688F29183F72@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <akOJ_sWgDVHlzWCN@arm.com>
Hi,
> Perhaps we should add an alias to __libc_malloc (and other malloc
> functions that GDB needs) for GDB, something like `__gdb_malloc`
> that would become Glibc's ABI for GDB? This is not ideal of course
> as GDB would need to look for this new symbol and than still fallback
> to 'malloc' to support other non-Glibc runtimes.
If the debugger just randomly changes malloc state, it's impossible to
debug memory or pointer issues...
So I don't believe it should use malloc or a different helper. String
arguments can be placed on the stack just like any other arguments
(within a reasonable limit - anything too large could simply be refused
just like a call with 1M arguments).
Cheers,
Wilco
next prev parent reply other threads:[~2026-06-30 9:50 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 [this message]
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=PAWPR08MB898253718529A2349688F29183F72@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