Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "László Benedek via Gdb" <gdb@sourceware.org>
To: "Balázs Samu Fekete" <balazs.samu.fekete@ericsson.com>,
	"Simon Marchi" <simon.marchi@polymtl.ca>,
	"Luis Machado" <luis.machado@linaro.org>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Do we still support DICOS?
Date: Mon, 2 Jun 2025 06:47:27 +0000	[thread overview]
Message-ID: <DB9PR07MB9152875EE7021909AD7C5449E662A@DB9PR07MB9152.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <2383362c-c833-41d2-bb85-6a59fe668c84@polymtl.ca>

Hi,

The Dicos product is still active but I am not longer associated with it. Let me forward this to someone (@Balázs Samu Fekete<mailto:balazs.samu.fekete@ericsson.com>) more knowledgeable.

Best regards,
Laszlo Benedek
Ericsson

________________________________
From: Simon Marchi <simon.marchi@polymtl.ca>
Sent: Friday, May 30, 2025 11:05 PM
To: Luis Machado <luis.machado@linaro.org>; László Benedek <laszlo.benedek@ericsson.com>; gdb@sourceware.org <gdb@sourceware.org>
Subject: Re: Do we still support DICOS?

On 2020-12-11 09:25, Luis Machado wrote:
> Hi,
>
> On 12/11/20 6:34 AM, László Benedek wrote:
>> Hi all,
>>
>> I am an Ericsson engineer working on a product that is the next version in the evolution of Dicos. This GDB support is still actively used in our products in Ericsson.
>> If it is possible please do not remove it from GDB.
>>
>> Thanks!
>>
>> Best regards,
>> Laszlo Benedek
>> Ericsson
>>
>> p.s.: I am not a subscriber on the gdb mail list, I was notified about this discussion. If you'd like to answer please cc me directly.
>
> Thanks for the update.
>
> It would be nice to have someone step up and be a maintainer of the "port" then, otherwise I think this question will be raised again in a couple years.
>
> If we have a name we can get in touch with, it makes it easier for us to verify the status of the code and prevent unwanted removals.

Hi László,

I stumbled on Dicos today, as I was working on a feature, so I thought
I'd do a check-in with you.  Can you confirm that the Dicos port is
still used?  Also, do you guys really use upstream GDB for this, not an
ancient version?  Given that there was no updates regarding Dicos in
many many years, I would actually be a bit surprised if the port hadn't
bit-rotten a little bit.

Thanks!

Simon

  reply	other threads:[~2025-06-02  6:49 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 [this message]
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
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=DB9PR07MB9152875EE7021909AD7C5449E662A@DB9PR07MB9152.eurprd07.prod.outlook.com \
    --to=gdb@sourceware.org \
    --cc=balazs.samu.fekete@ericsson.com \
    --cc=laszlo.benedek@ericsson.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