Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dlv dap: long-running server that doesn't terminate on disconnect and accepts new clients to launch/attach to new process #2329

Closed
polinasok opened this issue Jan 28, 2021 · 1 comment

Comments

@polinasok
Copy link
Collaborator

The current dlv-dap server is a single-use server. On disconnect, it not only stops the client connection, but also terminates itself.

DAP/Vscode devs have advised us that when using a debug adapter that is a server, we do not launch a new instance for every debug session/process, but instead have a long-running server. On disconnect, this server would shut down the debug session, close the client connection, and continue running. It can then accept a new client connection when a new session is triggered and would respond to launches/attach request to trace a new process every time.

Apparently this what the Java extension does. It is integrated with a long-running Java language server that also serves DAP and acts as a debug adapter. The server is started as soon as a Java project is opened and runs until VSCode is shut down. Each new DAP session results in a new connection to the server (code).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants