Debug Adapter Launch results in "Broken pipe" error from DAP server when sending back reply of "terminate" request #976
-
Hello everyone, Within the Eclipse Epsilon project, we've started to experiment with the Debug Adapter Protocol, so we can expose debugging capabilities outside Eclipse. I've got a toy version of a debug adapter and a socket-based server. I've got it to launch an Epsilon program through an LSP4E "Debug Adapter Launch" launch configuration. It's a pretty minimalistic one. It connects to a running server on {
"command": "launch",
"eolScript": "/home/antonio/testLSP.eol"
} The program completes its execution normally, and I can see the program terminated with an exit value of 0 in the Debug tab, but I always end up seeing this error message in my DAP server when the program finishes running:
Using an exception breakpoint, I saw that these exceptions appear to be thrown while trying to send back the replies to the terminate and disconnect requests, and also the errors reported from the failure to send those replies. I've listed the messages below. At this point, I'm not sure if I've misunderstood how to process the terminate/disconnect DAP requests or how to write the DAP server, or if this is a known issue in LSP4E. Any help would be appreciated :-). I've mostly been imitating what I've seen in other debug adapters so far (specifically, the XSLT and Rascal ones). If it helps, I've also listed the versions of LSP4E and LSP4J I'm using in our target platform. Best, Target platform definition fragment for LSP4E and LSP4JMessages which fail to be sent back
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Please ignore the above message: I have put a bit more work on the server (switching it to |
Beta Was this translation helpful? Give feedback.
Please ignore the above message: I have put a bit more work on the server (switching it to
attach
rather thanlaunch
) and how it deals with shutdown, and it doesn't exhibit the above errors anymore.