| [cdt-dev] gdb debug adapter (was RE: CDT on Github) |
|
BTW, I started a gdb debug adapter at QNX and have someone working on it here. We’d be happy to contribute that as the starting point. We’re closely following what CDT currently does with MI and is probably derived anyway
☺. It’s written in TypeScript and runs on node.js, which makes it really easy to plug into VS Code and Theia. We’ll need to figure out the best approach for CDT/LSP4E.debug. We could add node as a dependency, like we have with the JRE. Other
Eclipse projects are starting to use npm packages. Will have to see how they are handling this. Doug. From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Doug Schaefer Cool, thanks Marc. Collaboration is the main goal, at least after building a great debug adapter
☺. I also have a feeling we are going to need to extend the protocol to reach feature parity to our existing CDT debug. This, of course will require work with the other clients and if we can reuse as much as possible
between them, at least with the _javascript_ clients, it would make sense to do that as well. Doug. From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Marc Dumais Hi Doug, Indeed, Theia, or eventually the C/C++ IDE product based on it, will also need an awesome gdb debug adapter. We have recently done some prototyping on this, where we got code-debug (https://github.com/WebFreak001/code-debug) to (minimally) run
on top of Theia's recent DAP contribution. We reached-out to the author, but he did not seem interested to make it multi-IDE, so we would probably need to fork it, if we want to do serious work on it, for Theia. That being said, it's ery early in the game and no final decision is made on our side. We are willing to consider other DAs, specially if there is good potential for
collaboration. I did have the same question as Marc-Andre, about doing this work as part of the existing CDT project. It seems that a more IDE-neutral "home" would be good, and more
likely to attract a wide array of IDE contributors. The project could still be under the Eclipse Foundation, but perhaps as a new project? Regards, Marc From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> Hey, Marc, while I have you here, I imagine Theia will also need a gdb debug adapter. There was certainly a lot of buzz on Theia at EclipseCon and it should be on our
list of supported IDEs as well. I actually think it does certain things better than VS Code and am giving it a serious look. Hopefully we can work together on it. Doug. From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Marc Dumais Hi there, " I find them awkward having to work in a fork that needs to be magically kept up to date and stuff" That's only true for non-committers, AFAIK. Committers should have required permissions to create branches on the main repo, so pull requests can originate from there,
rather than a fork, if preferred.
Marc From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> Good question. For the new repos, it would be Github Issues and Pull Requests. I actually find their Issues better than bugzilla. But I've never been a fan of Pull Requests,
mainly because I find them awkward having to work in a fork that needs to be magically kept up to date and stuff. But that's how Github works and that's where most new open source projects end up. Working in VS Code and the _javascript_ world in general has
been eye-opening on that. |