From: Tom Tromey <tom@tromey.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Yury Khrustalev <Yury.Khrustalev@arm.com>,
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: Wed, 22 Jul 2026 07:36:54 -0600 [thread overview]
Message-ID: <87ldb3rvrd.fsf@tromey.com> (raw)
In-Reply-To: <lhujyqo9lfb.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Tue, 21 Jul 2026 21:45:12 +0200")
>>>>> Florian Weimer <fweimer@redhat.com> writes:
Florian> Does GDB ever free the copy of the literal?
>> No. I think there's a bug open about this but it's never seemed
>> important to fix.
> This is perhaps the main reason for using malloc? The proper lifetime
> of the literal is unclear, so it can never be deallocated, and using
> malloc at least avoids wasting a full page?
gdb has used malloc for this since well before I worked on gdb, like
decades before. Probably the rationale has been lost.
Anyway, yes, I think one reason this isn't fixed is that it's not clear
when the memory ought to freed. Also AFAIK this has never been a real
issue in practice.
Tom
next prev parent reply other threads:[~2026-07-22 13:37 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 [this message]
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=87ldb3rvrd.fsf@tromey.com \
--to=tom@tromey.com \
--cc=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=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