Debugging And Analyzing Go Code

<p>I came across this page on <a href="https://golang.org/doc/gdb" rel="nofollow">Debugging Go Code with GDB </a> on the official site. It has a negative impression of gdb in general.</p> <p>I was curious to know which debuggers Go programmers use for production purposes. What sort of tools and methods have Go programmers found very useful on a regular basis when it comes to analyzing and debugging their Go code?</p> <hr/>**评论：**<br/><br/>mauilion: <pre><p><a href="https://github.com/derekparker/delve" rel="nofollow">https://github.com/derekparker/delve</a></p> <p>Seems to be gaining popularity.</p></pre>recurrency: <pre><p><a href="http://www.informit.com/articles/article.aspx?p=1941206" rel="nofollow">http://www.informit.com/articles/article.aspx?p=1941206</a> — scroll down to &#34;Advice&#34;</p></pre>countzero: <pre><p>delve and Visual Code are my regular basis tool to debug go, and also fmt.Printf.</p></pre>hackworks: <pre><p>Having to configure in vscode for each target is a hassle. Wish there is some sort of dynamic template with variables to make it more generic. </p></pre>arp242: <pre><p><code>fmt.Printf()</code></p></pre>The_Sly_Marbo: <pre><p>Seriously, with its support for options like <code>%x</code> for raw bytes, <code>%#v</code> for complex structures, and <code>%T</code> for showing underlying types, <code>fmt.Printf()</code> has never let me down while debugging.</p></pre>