Hi Dobrin,
Thank you for speaking up. It is great to hear from the extended CDT community and great to see that many people are reading the emails on the dev list!
At the moment there is no plan to deprecate DSF or GDB's specific implementation, DSF-GDB. At the CDT summit in Nov 2018 a rough plan on the future of Eclipse CDT was created, this involved leveraging new technologies, in particular Debug Adapters and Languages Servers. Currently I and others are in process of experimenting with that. Of course, anything actively being contributed, maintained, etc will not be deprecated or removed from CDT. This of course includes DSF if the community continues to maintain it. I hope and expect to be around to maintain it for the coming years, but once debug adapters are working at parity then personally I will be encouraging users and extenders to try that too.
> The link you pointed at looks GDB specific: CDT-GDB-ADAPTER?
That is the GDB specific one, the debug adapter protocol (DAP) is the generic case and the generic implementation in Eclipse is done by LSP4E. So I would hazard to guess that if and when you are looking at DAP for your debugger that it will have the same relationship to LSP4E/DAP as you do now to DSF. There are some interesting cases to handle - e.g. where should the disassembly view live?
I find this conversation very informative and I am glad you are joining it as it is good to fully understand the lifecycle of extenders. Gidi's case shows that there can be a lag of many many years between changes in CDT and the community adopting/adapting to these changes.
What version of CDT are you testing & releasing against?
Thanks,
Jonah