I suspect there might be some other DAP non-compliance related to shutting down the debugger while it is starting.
I'm just reproducing @fendor 's usecase from #320, and I'm doing it too in VSCode, hoping to make any investigation easier.
Here's a couple of scenarii where I launch the debugger and then click "Stop" (Shift+F5) at various moments/in various ways:
-
soon after having started it (say after a second)
in the terminal window I see this:
hdb: Uncaught exception ghc-internal:GHC.Internal.IO.Exception.IOException:
Network.Socket.connect: <socket: 13>: does not exist (Connection refused)
HasCallStack backtrace:
ioError, called at ./Network/Socket/Internal.hs:224:5 in network-3.2.8.0-b69fc14ab47eb0f284d8e20e170e9ec0944dab54cb9a1b6cf51ab712a07bab38:Network.Socket.Internal
in the output window, I see this (sorry, I used to upload to https://0x0.st/, but they've disabled it; what are you using nowadays? For now, I'm relying on my Dropbox)
-
after a few more seconds, but clicking "Stop" twice
in the terminal window I see this:
hdb: Uncaught exception ghc-internal:GHC.Internal.IO.Exception.IOException:
GHCi.Message.readPipe: end of file
HasCallStack backtrace:
collectExceptionAnnotation, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:170:37 in ghc-internal:GHC.Internal.Exception
toExceptionWithBacktrace, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:90:42 in ghc-internal:GHC.Internal.Exception
throw, called at libraries/ghci/GHCi/Message.hs:721:16 in ghci-9.14.1-953d:GHCi.Message
in the output window, I see this
-
waiting a bit more, and clicking "Stop" twice, I got this
hdb: Uncaught exception ghc-internal:GHC.Internal.IO.Exception.IOException:
<socket: 13>: hClose: resource vanished (Broken pipe)
HasCallStack backtrace:
ioError, called at libraries/ghc-internal/src/GHC/Internal/IO/Handle/Internals.hs:887:17 in ghc-internal:GHC.Internal.IO.Handle.Internals
(tell me if you need the output).
I suspect there might be some other DAP non-compliance related to shutting down the debugger while it is starting.
I'm just reproducing @fendor 's usecase from #320, and I'm doing it too in VSCode, hoping to make any investigation easier.
Here's a couple of scenarii where I launch the debugger and then click "Stop" (Shift+F5) at various moments/in various ways:
soon after having started it (say after a second)
in the terminal window I see this:
in the output window, I see this (sorry, I used to upload to https://0x0.st/, but they've disabled it; what are you using nowadays? For now, I'm relying on my Dropbox)
after a few more seconds, but clicking "Stop" twice
in the terminal window I see this:
in the output window, I see this
waiting a bit more, and clicking "Stop" twice, I got this
(tell me if you need the output).