Comparison with eclipse-cdt/cdt-gdb-adapter ?

[mickaelistria]

Type: Debugger

I've posted the dual question to eclipse-cdt-cloud/cdt-gdb-adapter#56 .
I'd like to get some inputs from both projects to sort out how they compare and -to be clear- which one I'm more likely to favor if we're in need of a GDB debug adapter in some of our products.

Basically, have you compared the debug adapter from VSCode-C++ extension with the incubating one from Eclipse CDT?
On eclipse-cdt-cloud/cdt-gdb-adapter#56 , it seems like missing registers and memory view are justification for a new debug adapter. What do you think? Is it actually missing? Would it be something that could be easily implemented in VSCode-C++ debug adapter?
Are there some synergies with https://platformio.org/platformio-ide which may grow the feature set of VSCode-C++ debug adapter?

[mickaelistria]

The vscode C++ debug adapter is actually not free software as licence on marketplace says «INSTALLATION AND USE RIGHTS. You may only use the C/C++ Extension for Visual Studio Code with Visual Studio Code, Visual Studio or Xamarin Studio software to help you develop and test your applications.», or is it only for a component in particular? (We want to use gdb,not vsdbg)
Can you please update the marletplace licence to get rid of this clause or change repo license as well as saying it's MIT isn't really compatible with this restrictive clause?

[WardenGnaw]

We have not used eclipse-cdt or platformio.

However for the memory view, we have an issue on the gdb adapter on creating a memory window: microsoft/MIEngine#816

The marketplace license is for the published extension. The cpptools source code is MIT License and if you are interested in the gdb adapter we have it also under the MIT license here: https://github.com/Microsoft/MIEngine

[github-actions]

This issue has been closed automatically because it's labeled as a 'question' and has not had recent activity.