Skip to content

Commit a2eae66

Browse files
mknyszekgopherbot
authored andcommitted
doc: add release notes for a couple minor tracing features
For #65614. Change-Id: I759bf671b8f84c5224798b0dfaee6b158fdcc95a Reviewed-on: https://go-review.googlesource.com/c/go/+/587927 Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Michael Knyszek <mknyszek@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
1 parent c506f03 commit a2eae66

File tree

2 files changed

+13
-0
lines changed

2 files changed

+13
-0
lines changed

doc/next/3-tools.md

+9
Original file line numberDiff line numberDiff line change
@@ -53,3 +53,12 @@ module whose go.mod file specifies `go 1.21`.
5353
[cmd/cgo] supports the new `-ldflags` flag for passing flags to the C linker.
5454
The `go` command uses it automatically, avoiding "argument list too long"
5555
errors with a very large `CGO_LDFLAGS`.
56+
57+
### Trace {#trace}
58+
59+
<!-- go.dev/issue/65316 -->
60+
The `trace` tool now better tolerates partially broken traces by attempting to
61+
recover what trace data it can. This functionality is particularly helpful when
62+
viewing a trace that was collected during a program crash, since the trace data
63+
leading up to the crash will now [be recoverable](/issue/65319) under most
64+
circumstances.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
<!-- go.dev/issue/65319 -->
2+
The runtime now explicitly flushes trace data when a program crashes due to an
3+
uncaught panic. This means that more complete trace data will be available in a
4+
trace if the program crashes while tracing is active.

0 commit comments

Comments
 (0)