Alessandro Arzilli 81781522c3 proc: make sure logical breakpoints map exists (#3115) ... The logical breakpoints map was created as a side effect of createUnrecoveredPanicBreakpoint or createFatalThrowBreakpoint, however with an executable with incomplete debug info (that must be incomplete in just the right way) both will fail and the logical breakpoint map will never be created. It's unknown how such an executable could be created, one easy way is to debug a non-go executable. Fixes #3114		2022-08-22 12:48:34 -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	proc: make sure logical breakpoints map exists (#3115)	2022-08-22 12:48:34 -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