<p>We're happy to announce the beta release of the <a href="https://cloud.google.com/tools/cloud-debugger/setting-up-go-on-compute-engine">Cloud Debugger for Go</a>. Cloud Debugger makes it easy for you to track down problems in your Go programs. Set a snapshot location and view application state when that line of code is executed. Includes support for conditional snapshot locations. See <a href="https://cloud.google.com/tools/cloud-debugger/debugging">Using Cloud Debugger</a> for more details.</p>
<p>Cloud Debugger adds zero overhead on Compute Engine projects that aren’t being actively debugged. It also adds less than 10ms to request latency when capturing application state without blocking requests to your application. </p>
<p>This release includes support for Go programs running on Compute Engine. We plan to bring this to other Google Cloud platforms in the future. As always, we’d love direct feedback to <a href="mailto:cdbg-feedback@google.com">cdbg-feedback@google.com</a> and will be monitoring <a href="http://stackoverflow.com/questions/tagged/google-compute-engine">Stack Overflow</a> for issues and suggestions.</p>
<hr/>**评论：**<br/><br/>dinkumator: <pre><p>Wow this is cool! Will any components of this be open-sourced with the rest of the go tools? It would be great to be able to debug things (better) locally without paying for compute time.</p></pre>jbuberel: <pre><p>Most of the heavy lifting is done by:</p>
<ul>
<li><a href="https://godoc.org/golang.org/x/debug/ogle">https://godoc.org/golang.org/x/debug/ogle</a></li>
<li><a href="https://godoc.org/golang.org/x/debug/dwarf">https://godoc.org/golang.org/x/debug/dwarf</a></li>
</ul>
<p>The small program that runs inside the GCE VM instance and monitors the running process - the debuglet - is in the process of being open sourced now. It should be available in a week or so.</p>
<p>Although the debuglet talks to a bunch of Google-cloud-only services to relay snapshot data, the basic framework should be re-usable in other environments. There is nothing particularly exotic being done.</p></pre>moinboin: <pre><p>Is there a screencast showing the debugger in action?</p></pre>jbuberel: <pre><p>Unfortunately not, and I wasn't able to convince the dev team to create one ;-)</p>
<p>Even though the code samples on this page are Java, the feature is nearly identical for Go. There are plenty of screen shots, etc:</p>
<p><a href="https://cloud.google.com/tools/cloud-debugger/debugging" rel="nofollow">https://cloud.google.com/tools/cloud-debugger/debugging</a></p></pre>sanatgersappa: <pre><p>w00t!</p></pre>bketelsen: <pre><p>NICE!</p></pre>nexusbees: <pre><p>This seems really cool! Does the debugger have any dependencies on other Google services/infra? If it doesn't, can it be replicated anywhere?</p></pre>jbuberel: <pre><p>Yes and no. The real work is all happening in <a href="https://godoc.org/golang.org/x/debug" rel="nofollow">https://godoc.org/golang.org/x/debug</a></p>
<p>The small Go program that runs inside the VM instance and monitors your process - called the debuglet - is in the process of being open sourced. It doesn't do much interesting stuff, it only relays protobufs between the Google-cloud backend services. However, it could easily be modified for other runtime environments.</p></pre>nexusbees: <pre><p>Thanks! Is there any info on the capabilities or pros/cons of this tool?</p></pre>divan0: <pre><p>Trying to test debugger with simple demo app, and got:</p>
<blockquote>
<p>You are viewing master, but debug target gcedebug-test-main-1.0 was deployed from master.
To debug this deployment, switch to master.</p>
</blockquote></pre>jbuberel: <pre><p>My only suggestion at this point is to do a full browser refresh/reload and see if the problem persists.</p></pre>
