qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-14 17:40:28 -07:00
Code Releases Activity

doc: add release notes for a couple minor tracing features

Browse Source 
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>
This commit is contained in:
Michael Anthony Knyszek 2024-05-24 18:46:48 +00:00 committed by Gopher Robot
parent c506f035d9
commit a2eae66c30
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/next/3-tools.md
View File

@ -53,3 +53,12 @@ module whose go.mod file specifies `go 1.21`.
[cmd/cgo] supports the new `-ldflags` flag for passing flags to the C linker.
The `go` command uses it automatically, avoiding "argument list too long"
errors with a very large `CGO_LDFLAGS`.
### Trace {#trace}
<!-- go.dev/issue/65316 -->
The `trace` tool now better tolerates partially broken traces by attempting to
recover what trace data it can. This functionality is particularly helpful when
viewing a trace that was collected during a program crash, since the trace data
leading up to the crash will now [be recoverable](/issue/65319) under most
circumstances.

4
doc/next/6-stdlib/99-minor/runtime/trace/65319.md Normal file
View File

@ -0,0 +1,4 @@
<!-- go.dev/issue/65319 -->
The runtime now explicitly flushes trace data when a program crashes due to an
uncaught panic. This means that more complete trace data will be available in a
trace if the program crashes while tracing is active.