aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYasuhiro Matsumoto <mattn.jp@gmail.com>2019-03-27 09:48:50 +0900
committerAndrew Bonventre <andybons@golang.org>2019-03-27 21:21:14 +0000
commit6bedf551f6d7d21cf7f656a0748ca65bf387b884 (patch)
tree7b82147189fdb7e9c528d04dd61022846a6ad1d3
parent6ad4468cace68a8d4c8b5a32209428e49b1b871d (diff)
content: include vim in list of editors that use delve
See https://github.com/fatih/vim-go/pull/1390 Change-Id: I59a45a207b68d08c53d4f16ff4240a28d145c1a1 Reviewed-on: https://go-review.googlesource.com/c/blog/+/169537 Reviewed-by: Austin Clements <austin@google.com>
-rw-r--r--content/debugging-what-you-deploy.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/debugging-what-you-deploy.article b/content/debugging-what-you-deploy.article
index 502b43e..b197359 100644
--- a/content/debugging-what-you-deploy.article
+++ b/content/debugging-what-you-deploy.article
@@ -18,7 +18,7 @@ For Go 1.11 and 1.12, we focused on improving the debugging experience on optimi
* Debugging optimized code with Delve
-[[https://github.com/go-delve/delve][Delve]] is a debugger for Go on x86 supporting both Linux and macOS. Delve is aware of goroutines and other Go features and provides one of the best Go debugging experiences. Delve is also the debugging engine behind [[https://www.jetbrains.com/go/][GoLand]] and [[https://code.visualstudio.com/][VS Code]].
+[[https://github.com/go-delve/delve][Delve]] is a debugger for Go on x86 supporting both Linux and macOS. Delve is aware of goroutines and other Go features and provides one of the best Go debugging experiences. Delve is also the debugging engine behind [[https://www.jetbrains.com/go/][GoLand]], [[https://code.visualstudio.com/][VS Code]], and [[https://github.com/fatih/vim-go][Vim]].
Delve normally rebuilds the code it is debugging with `-gcflags`"all=-N`-l"`, which disables inlining and most optimizations. To debug optimized code with delve, first build the optimized binary, then use `dlv`exec`your_program` to debug it. Or, if you have a core file from a crash, you can examine it with `dlv`core`your_program`your_core`. With 1.12 and the latest Delve releases, you should be able to examine many variables, even in optimized binaries.