From: Tom Tromey <tom@tromey.com>
To: Matthieu Longo <matthieu.longo@arm.com>
Cc: Luis <luis.machado.foss@gmail.com>,
gdb-patches@sourceware.org,
Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
Andrew Burgess <aburgess@redhat.com>,
Luis Machado <luis.machado@amd.com>
Subject: Re: [PATCH] gdb questions: fallback on maps still relevant today ?
Date: Tue, 21 Jul 2026 10:55:27 -0600 [thread overview]
Message-ID: <87zezkuvsw.fsf@tromey.com> (raw)
In-Reply-To: <a4c42d44-91ff-461a-acec-d03cff68e850@arm.com> (Matthieu Longo's message of "Wed, 1 Jul 2026 14:34:49 +0100")
>> That´d be fine by me. We might want to do the deprecation dance and
>> then drop from a future release.
Matthieu> What do you mean by "deprecation dance" ?
Matthieu> What would the steps be to get rid of this fallback ?
A kind of normal thing to do would be to warn users that this is going
to happen, and then make the change in release N+1.
Another approach though might be to just remove the code, since it's so
very old, and then have a fallback that warns if smaps is not found but
maps is.
gdb frequently struggles with removing dead code. We're not always sure
it's truly dead, and some people out there run weird and/or antique
setups.
Tom
prev parent reply other threads:[~2026-07-21 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 12:17 Matthieu Longo
2026-07-01 12:33 ` Luis
2026-07-01 13:34 ` Matthieu Longo
2026-07-21 16:55 ` Tom Tromey [this message]
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=87zezkuvsw.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=luis.machado@amd.com \
--cc=matthieu.longo@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