From d813551f824b6fec0462641ad4ea58f64abe1289 Mon Sep 17 00:00:00 2001 From: Fuminori Sakamoto Date: Wed, 24 Apr 2019 06:55:36 +0900 Subject: [PATCH] fix go-delve URL (#1142) --- docs/usage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/usage.md b/docs/usage.md index 8fb6b5fecd6d..59548cf95ccd 100644 --- a/docs/usage.md +++ b/docs/usage.md @@ -451,7 +451,7 @@ Debugging Golang functions Golang function debugging is slightly different when compared to Node.JS, Java, and Python. We require -[delve](https://github.com/derekparker/delve) as the debugger, and wrap +[delve](https://github.com/go-delve/delve) as the debugger, and wrap your function with it at runtime. The debugger is run in headless mode, listening on the debug port. @@ -463,7 +463,7 @@ You must compile [delve]{.title-ref} to run in the container and provide its local path via the [\--debugger-path]{.title-ref} argument. Build delve locally as follows: -`GOARCH=amd64 GOOS=linux go build -o /dlv github.com/derekparker/delve/cmd/dlv` +`GOARCH=amd64 GOOS=linux go build -o /dlv github.com/go-delve/delve/cmd/dlv` NOTE: The output path needs to end in [/dlv]{.title-ref}. The docker container will expect the dlv binary to be in the \