public inbox for
 help / color / mirror / Atom feed
From: Simon Marchi <>
To: "" <>
Subject: Proposal to Removal of QNX Neutrino support from GDB
Date: Fri, 11 Dec 2020 09:47:04 -0500	[thread overview]
Message-ID: <> (raw)


Given that:

- there hasn't been contributions to the QNX Neutrino port for a while [1]
- there is no maintainer for it
- the tools to build and run QNX programs are not publicly available for
  anybody to test this support

I propose to remove QNX Neutrino support from GDB for GDB 12.  That means
the support would still be included in GDB 11, the next release, and removed
just after the GDB 11 branch is created.

There are two parts to it:

1. Native bits for when GDB itself runs on Neutrino (nto-procfs.c)
2. Neutrino target support (nto-tdep.c and friends)

We can't compile #1, as that requires the Neutrino SDK.  We can build-test
#2, as it doesn't require Neutrino-specific include files, but we can't run
it.  The current plan is to remove both.  But if Neutrino target support
(#2) is still being used (say, with a custom remote target), but native
support (#1) isn't, one option is to only remove the native bits, so we only
keep the part that anybody can at least build.

If somebody would like the support for Neutrino to stay in GDB, please speak up.
If so, we will need a maintainer to step up and become responsible to that port.

There is a patch series that implement the proposal here:



[1] Last one was d7161de46af ("[nto] Improve ABI sniffing.")

             reply	other threads:[~2020-12-11 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 14:47 Simon Marchi [this message]
2020-12-11 17:31 ` Stephen Webb
2020-12-11 17:52   ` Simon Marchi
2021-02-25 21:16     ` Simon Marchi
2021-02-27 15:48       ` Stephen Webb
2021-02-28 15:28         ` Simon Marchi
2021-03-01 16:45           ` Simon Marchi
2021-08-04 14:51             ` Simon Marchi
2021-08-04 15:14               ` Stephen Webb
2021-08-04 17:21                 ` Simon Marchi
2021-08-04 19:47                   ` Luis Machado
2022-04-05 14:30                   ` Simon Marchi
2023-03-28 19:24                 ` Simon Marchi

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).