Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>
To: Eli Zaretskii <eliz@gnu.org>, Simon Marchi <simark@simark.ca>
Cc: tom@tromey.com, tdevries@suse.de, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/python] Use PyConfig for python 3.9
Date: Wed, 12 Nov 2025 16:52:13 +0000	[thread overview]
Message-ID: <18cba048-250a-47a9-a056-8a4e255b7fa5@arm.com> (raw)
In-Reply-To: <865xbrgeo2.fsf@gnu.org>

On 03/11/2025 18:21, Eli Zaretskii wrote:
>> Date: Mon, 3 Nov 2025 12:09:05 -0500
>> Cc: tdevries@suse.de, gdb-patches@sourceware.org
>> From: Simon Marchi <simark@simark.ca>
>>
>>> We can discuss the broader issue of whether we want to drop support
>>> for XP, yes.  When we do, please explain how supporting it holds back
>>> GNU development, as the basis for the discussion, and let's take it
>>> from there.
>>
>> One possibility is to declare that it's no longer possible to compile
>> GDB with Python support, on Windows XP, because we want to make use of
>> Python features newer that the latest Python that works on XP.
> 
> IMO, that's not a good idea, because Python support is nowadays
> considered a de-facto integral part of GDB.  For example, the .gdbinit
> file shipped with GNU Emacs uses Python without even testing that it's
> available.
> 
> Btw, the problem is not the system where GDB is compiled, the problem
> is the system on which it runs.

So how long are we expected to support such an antiquated system?  It's already 11 years beyond it's final maintenance update and continuing to pretend we can support it is clearly holding up development of gdb.

If the runtime can't support critical improvements of gdb, then surely it's time to reconsider our priorities.  We're not stopping people from running older versions of gdb after all.

R.

  reply	other threads:[~2025-11-12 16:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 13:36 Tom de Vries
2025-10-17 14:13 ` Tom Tromey
2025-10-17 15:11   ` Eli Zaretskii
2025-10-17 16:33     ` Tom Tromey
2025-10-17 18:34       ` Eli Zaretskii
2025-10-31 18:15         ` Tom Tromey
2025-11-01  7:00           ` Eli Zaretskii
2025-11-03 17:09             ` Simon Marchi
2025-11-03 18:21               ` Eli Zaretskii
2025-11-12 16:52                 ` Richard Earnshaw (foss) [this message]
2025-11-12 17:23                   ` Eli Zaretskii
2025-11-12 17:53                     ` Richard Earnshaw (foss)
2025-11-12 18:03                     ` Arsen Arsenović
2025-11-12 18:20                       ` Eli Zaretskii
2025-11-12 19:24                         ` Arsen Arsenović
2025-11-13  5:45                           ` Eli Zaretskii
2025-10-17 16:51     ` Arsen Arsenović
2025-10-17 18:35       ` Eli Zaretskii

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=18cba048-250a-47a9-a056-8a4e255b7fa5@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    /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