Alessandro Arzilli 5b9f65dac2 *: switch to int64 for goroutine IDs (#3110) ... Go 1.20 switched to uint64 to represent goroutine IDs, we can't actually follow suit because we have allowed clients to use -1 to refer to the currently selected goroutine, however we should at least switch to int64 and also update the rtype check to accept the 1.20 type.		2022-08-16 09:31:11 -07:00
..
api	*: switch to int64 for goroutine IDs (#3110)	2022-08-16 09:31:11 -07:00
dap	*: switch to int64 for goroutine IDs (#3110)	2022-08-16 09:31:11 -07:00
debugger	*: switch to int64 for goroutine IDs (#3110)	2022-08-16 09:31:11 -07:00
internal/sameuser	fmt code (#2826)	2021-12-13 10:25:23 -08:00
rpc1	*: switch to int64 for goroutine IDs (#3110)	2022-08-16 09:31:11 -07:00
rpc2	*: switch to int64 for goroutine IDs (#3110)	2022-08-16 09:31:11 -07:00
rpccommon	*: run go1.19 'go fmt' on everything and fix problems (#3031)	2022-06-17 10:08:11 -07:00
test	*: switch to int64 for goroutine IDs (#3110)	2022-08-16 09:31:11 -07:00
client.go	*: switch to int64 for goroutine IDs (#3110)	2022-08-16 09:31:11 -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-*: conform to godoc comments (#2916)	2022-03-09 09:12:42 -08:00
server.go	cmd,service: remove temporary def of Server interface in func	2018-10-09 07:56:48 -07:00