Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>,
	 simark@simark.ca, 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 19:03:01 +0100	[thread overview]
Message-ID: <867bvvxh62.fsf@aarsen.me> (raw)
In-Reply-To: <86seejrwpg.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Wed, 12 Nov 2025 16:52:13 +0000
>> Cc: tom@tromey.com, tdevries@suse.de, gdb-patches@sourceware.org
>> From: "Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>
>> 
>> > 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?
>
> I think that depends on what is required to "support" them.  That's
> what we should talk about, and in practical terms.  E.g., if all
> that's required is not to delete compatibility code (and I'm not
> saying that's all, I'm just giving an example), it is my opinion that
> the effort is negligible.

I think that, for Windows XP, the repetition of this conversation any
time someone wants to use something that doesn't work on XP is reason
enough to remove it.

It's a proprietary OS even its vendor abandoned 11 years ago.  The
milliwatts spent composing this email are enough to justify ignoring it
further.  The remaining users are likely computers not used
interactively, and near-certainly not ones used for development, ergo a
debugger is redundant.

Frankly, a Windows XP machine that has enough networking hardware to
download the next release of GDB is likely a massive liability in the
first place.  Hopefully none are still connected to the internet.
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 418 bytes --]

  parent reply	other threads:[~2025-11-12 18:03 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)
2025-11-12 17:23                   ` Eli Zaretskii
2025-11-12 17:53                     ` Richard Earnshaw (foss)
2025-11-12 18:03                     ` Arsen Arsenović [this message]
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=867bvvxh62.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=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