From 4aea3f6fee166fa29115fd3f29469a35d5a12bce Mon Sep 17 00:00:00 2001
From: David Symonds <dsymonds@golang.org>
Date: Tue, 3 Jun 2014 11:16:35 +1000
Subject: [PATCH] [release-branch.go1.3] doc: mention WriteHeapDump in 1.3
 release notes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

««« CL 103810044 / 603f6c3b152c
doc: mention WriteHeapDump in 1.3 release notes

LGTM=r
R=khr, r
CC=golang-codereviews
https://golang.org/cl/103810044
»»»

TBR=adg
R=adg
CC=golang-codereviews
https://golang.org/cl/99700043
---
 doc/go1.3.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/go1.3.html b/doc/go1.3.html
index b22443ef06..685d233105 100644
--- a/doc/go1.3.html
+++ b/doc/go1.3.html
@@ -539,6 +539,12 @@ Earlier versions of Go handled this situation inconsistently: most instances
 were reported as deadlocks, but some trivial cases exited cleanly instead.
 </li>
 
+<li>
+The runtime/debug package now has a new function
+<a href="/pkg/runtime/debug/#WriteHeapDump"><code>debug.WriteHeapDump</code></a>
+that writes out a description of the heap.
+</li>
+
 <li>
 The <a href="/pkg/strconv/#CanBackquote"><code>CanBackquote</code></a>
 function in the <a href="/pkg/strconv/"><code>strconv</code></a> package
-- 
2.50.0