From: Luis Machado <luis.machado@linaro.org>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, gdbserver: remove WinCE support code
Date: Mon, 12 Apr 2021 10:57:03 -0300 [thread overview]
Message-ID: <add7223b-b8ec-8aeb-d5d2-69aa5131ee2f@linaro.org> (raw)
In-Reply-To: <20210410231021.1232451-1-simon.marchi@polymtl.ca>
On 4/10/21 8:10 PM, Simon Marchi via Gdb-patches wrote:
> The support for WinCE was removed with commit 84b300de3666 ("gdbserver:
> remove support for ARM/WinCE"). There is some leftover code for WinCE
> support, guarded by the _WIN32_WCE macro, which I didn't know of at the
> time.
>
> I didn't remove the _WIN32_WCE references in the tests, because in
> theory we still support the WinCE architecture in GDB (when debugging
> remotely). So someone could run a test with that (although I'd be
> really surprised).
Is there value in supporting remote-based debugging of WinCE if we're
dropping gdbserver support? Should we also drop the GDB and testing
parts given this won't likely be exercised anytime soon if there's no
maintainer?
next prev parent reply other threads:[~2021-04-12 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 23:10 Simon Marchi
2021-04-12 11:42 ` Pedro Alves
2021-04-12 15:12 ` Simon Marchi
2021-04-12 15:24 ` Simon Marchi
2021-04-12 22:20 ` [PATCH] Remove process_stratum_target::hostio_last_error abstraction (Re: [PATCH] gdb, gdbserver: remove WinCE support code) Pedro Alves
2021-04-12 22:52 ` Pedro Alves
2021-04-12 23:56 ` Simon Marchi
2021-04-13 13:12 ` Pedro Alves
2021-04-12 13:57 ` Luis Machado [this message]
2021-04-12 14:01 ` [PATCH] gdb, gdbserver: remove WinCE support code Simon Marchi
2021-04-12 14:07 ` Luis Machado
2021-04-13 19:29 ` Tom Tromey
2021-04-13 21:14 ` Pedro Alves
2021-04-13 21:20 ` [pushed] Remove WinCE code from gdbreplay Pedro Alves
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=add7223b-b8ec-8aeb-d5d2-69aa5131ee2f@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).