From: Simon Marchi <simon.marchi@polymtl.ca>
To: "László Benedek" <laszlo.benedek@ericsson.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
"luis.machado@linaro.org" <luis.machado@linaro.org>
Subject: Re: Do we still support DICOS?
Date: Fri, 11 Dec 2020 09:18:19 -0500 [thread overview]
Message-ID: <2f11e8e6-10b4-0a45-8e18-bcc32073c508@polymtl.ca> (raw)
In-Reply-To: <AM6PR07MB6102F20D9ED73017EBD51371E6CA0@AM6PR07MB6102.eurprd07.prod.outlook.com>
On 2020-12-11 4:34 a.m., László Benedek via Gdb 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.
>
Ok, thanks for the notice, that helps us know that it is still relevant.
There hasn't been any contribution related to Dicos in a while, so we weren't sure. If
you stumble on any problem, don't hesitate to try to contribute fixes upstream, that way
we know that the platform is being used (and you don't have to maintain patches on the
side).
For others, here's the original thread:
https://sourceware.org/pipermail/gdb/2020-September/048925.html
Simon
next prev parent reply other threads:[~2020-12-11 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 9:34 László Benedek
2020-12-11 14:18 ` Simon Marchi [this message]
2020-12-11 14:25 ` Luis Machado
2020-12-11 14:25 ` Luis Machado
-- 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=2f11e8e6-10b4-0a45-8e18-bcc32073c508@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=laszlo.benedek@ericsson.com \
--cc=luis.machado@linaro.org \
/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).