Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lsp4e-dev] Preferred way to add a Debug Adapter support
HI Mikael,

> Is this what would be the expected work for best integration of Debug Adapter?

Yes this is what I expect for easiest use, it corresponds to 1 below. There are two options to go about this (this is from the upcoming newsletter):

To create your own Eclipse plug-in that uses LSP4E’s Debug implementation you have two choices:

  1. Contribute to the launch configuration extension point, using the LSP4E’s DSPLaunchDelegate as the delegate. This requires saving into the launch configuration command, arguments and json launch parameters using the launch configuration keys defined in the DSPPlugin.

  2. Contribute to the launch configuration extension point using a custom launch delegate. Within the launch delegate, create a DSPDebugTarget and call initialize() on it to start the processing.

The advantage to option 1 is more reuse of some tricky code to launch and trace a debug adapter. The advantage of option 2 is DSPDebugTarget receives a Map and therefore clients of DSPDebugTarget do not have to use/store JSON in their launch configuration.



I hope that answers your question.

Jonah


~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On Fri, 29 Jun 2018 at 07:17, Mickael Istria <mistria@xxxxxxxxxx> wrote:
Hi all, and more particularly Jonah ;)

Yesterday, I could have the netcoredbg from Samsung working to debug C# projects: https://github.com/eclipse/aCute/issues/102#issuecomment-401191714 . That would be an extremely useful functionality for aCute users and would make C# in Eclipse IDE a really achievable story (so far, lack of debug made the project not so profitable for users compared to competitors). I also like the fact that this is an opportunity to have on Eclipse.org project in the release train relying on DAP and thus validating the lsp4e.debug support and having a 1st case other can be inspired from.
It's important to acknowledge here that the netcoredbg project developers have been very helpful and reactive to our requests to make it happen and that most of the real work comes from them.

Now, I'd like to consider shipping this debugger with aCute. It seems to me that as an integrator of this debugger, the natural next step is to create a dedicated ".Net Debug Configuration" which would use the DSPLaunchDelegate but just customize the main tab to make it more specific, easier and less error-prone.
Is this what would be the expected work for best integration of Debug Adapter? Or is there another way to bind things you'd recommend?

Thanks in advance for your advice!

--
Mickael Istria
Eclipse IDE developer, for Red Hat Developers
_______________________________________________
lsp4e-dev mailing list
lsp4e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/lsp4e-dev

Back to the top