mirror of
https://github.com/golang/go.git
synced 2026-02-07 03:15:05 +03:00
cmd/trace: fix typo in web documentation
Change-Id: I950224c3f698fbdf2bcab6f847f4afddaa6e9c2d Reviewed-on: https://go-review.googlesource.com/c/go/+/416974 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> Run-TryBot: Alan Donovan <adonovan@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Reviewed-by: Alan Donovan <adonovan@google.com>
This commit is contained in:
committed by
Tobias Klauser
parent
7510e597de
commit
b75ad09cae
@@ -247,7 +247,7 @@ p { color: grey85; font-size:85%; }
|
||||
because it made a system call or tried to acquire a mutex.
|
||||
|
||||
Directly underneath each bar, a smaller bar or more commonly a fine
|
||||
vertical line indicates an event occuring during its execution.
|
||||
vertical line indicates an event occurring during its execution.
|
||||
Some of these are related to garbage collection; most indicate that
|
||||
a goroutine yielded its logical processor but then immediately resumed execution
|
||||
on the same logical processor. Clicking on the event displays the stack trace
|
||||
@@ -274,7 +274,7 @@ p { color: grey85; font-size:85%; }
|
||||
function written in C.
|
||||
</p>
|
||||
<p>
|
||||
Above the event trace for the first logical processor are
|
||||
Above the event trace for the first logical processor are
|
||||
traces for various runtime-internal events.
|
||||
|
||||
The "GC" bar shows when the garbage collector is running, and in which stage.
|
||||
|
||||
Reference in New Issue
Block a user