Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb <gdb@sourceware.org>
To: "Balázs Samu Fekete" <balazs.samu.fekete@ericsson.com>,
	"Luis Machado" <luis.machado@arm.com>,
	"Luis Machado" <luis.machado@linaro.org>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Do we still support DICOS?
Date: Wed, 18 Jun 2025 10:37:34 -0400	[thread overview]
Message-ID: <f5a70ef5-1ef5-412c-8796-8cef488a3f93@polymtl.ca> (raw)
In-Reply-To: <PAWPR07MB9484CF39FB29B7DBECB6CFC5B873A@PAWPR07MB9484.eurprd07.prod.outlook.com>

On 6/17/25 2:13 AM, Balázs Samu Fekete wrote:
> Hi
> 
> I don't know what it would mean to have a maintaner, or how that works in general, but you can contact me with any issues regarding the port.

It would be good to list dicos in the MAINTAINERS file, with you as the
maintainer, where all the "--target..." are listed.  I'm not sure what
the exact triplet(s) would be though.  Can you propose a patch that add
dicos (with you as the maintainer) to that list?

It is a good idea to do some testing of your port whenever a new version
is about to be released (for instance, GDB 17 will branch soon).
Especially since your port works unlike any others, w.r.t. shared
libraries, so it could break and nobody will notice.

There has been no changes related to Dicos for many years, so I'm
actually kind of surprised that the port worked flawlessly for all this
time.  Good news I guess.

Finally, if you have any downstream fixes, I would encourage you to
submit them upstream.  It will show that the port is actively used.

Simon

  reply	other threads:[~2025-06-18 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  9:34 László Benedek via Gdb
2020-12-11 14:18 ` Simon Marchi via Gdb
2020-12-11 14:25 ` Luis Machado via Gdb
2025-05-30 21:05   ` Simon Marchi via Gdb
2025-06-02  6:47     ` László Benedek via Gdb
2025-06-02  6:57       ` Balázs Samu Fekete via Gdb
2025-06-02  7:32         ` Luis Machado via Gdb
2025-06-17  6:13           ` Balázs Samu Fekete via Gdb
2025-06-18 14:37             ` Simon Marchi via Gdb [this message]
2020-12-11 14:25 ` Luis Machado via Gdb
  -- strict thread matches above, loose matches on Subject: below --
2020-09-22 19:01 Luis Machado
2020-09-29 12:16 ` 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=f5a70ef5-1ef5-412c-8796-8cef488a3f93@polymtl.ca \
    --to=gdb@sourceware.org \
    --cc=balazs.samu.fekete@ericsson.com \
    --cc=luis.machado@arm.com \
    --cc=luis.machado@linaro.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