delve/service
polinasok b7d8edcdaf
service/dap: handle unexpected debugger termination (EOF) error (#2574)
Using issue419.go, I observed that the continue command fails with an error when debugger receives and forwards an interrupt. In spite of the stopped event, vscode still shows the state as RUNNING because the threads request is unable to retrieve any threads, but at least one dummy thread is always expected.

Co-authored-by: Polina Sokolova <polinasok@users.noreply.github.com>
2021-07-22 08:52:04 -07:00
..
api proc: allow multiple overlapping internal breakpoints (#2519) 2021-07-21 08:24:19 -07:00
dap service/dap: handle unexpected debugger termination (EOF) error (#2574) 2021-07-22 08:52:04 -07:00
debugger proc: allow multiple overlapping internal breakpoints (#2519) 2021-07-21 08:24:19 -07:00
internal/sameuser sameuser: log the uid/remoteUID when they are not matching (#2535) 2021-06-15 15:36:39 +02:00
rpc1 Go 1.17 support branch (#2451) 2021-07-08 08:47:53 -07:00
rpc2 service/rpc2: Fix panic in ListDynamicLibraries (#2586) 2021-07-14 18:28:54 +02:00
rpccommon dap: add sameuser check (#2494) 2021-05-19 10:29:05 -07:00
test proc: allow multiple overlapping internal breakpoints (#2519) 2021-07-21 08:24:19 -07:00
client.go terminal,service: Add filtering and grouping to goroutines command (#2504) 2021-07-01 11:25:33 -07:00
config.go cmd/dlv: Fix trace output (#2038) 2020-05-13 08:38:10 +02:00
listenerpipe.go cmd,service: in non-headless mode use an in-memory connection 2018-10-08 15:11:13 -07:00
rpccallback.go service: serialize calls to Command API (#2370) 2021-03-08 10:05:10 -08:00
server.go cmd,service: remove temporary def of Server interface in func 2018-10-09 07:56:48 -07:00