From 96b99cf72489877005e208f3386ab1bb9c6541ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Thu, 18 Mar 2021 11:03:11 +0100 Subject: [PATCH] minor edits --- block.md | 2 +- goroutine.md | 2 +- stack-traces.md | 10 +++++----- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/block.md b/block.md index 2b9a224..2f4f95e 100644 --- a/block.md +++ b/block.md @@ -271,4 +271,4 @@ Block profiling was [implemented](https://codereview.appspot.com/6443115) by [Dm I'm [felixge](https://github.com/felixge) and work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out. We're also [hiring](https://www.datadoghq.com/jobs-engineering/#all&all_locations) : ). -The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome! \ No newline at end of file +The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome! diff --git a/goroutine.md b/goroutine.md index 9eaf200..1ab23d4 100644 --- a/goroutine.md +++ b/goroutine.md @@ -241,4 +241,4 @@ Goroutine profiling was [implemented](https://codereview.appspot.com/5687076/) b I'm [felixge](https://github.com/felixge) and work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out. We're also [hiring](https://www.datadoghq.com/jobs-engineering/#all&all_locations) : ). -The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome! \ No newline at end of file +The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome! diff --git a/stack-traces.md b/stack-traces.md index 4c4ddbd..aadd2ee 100644 --- a/stack-traces.md +++ b/stack-traces.md @@ -6,11 +6,11 @@ Stack traces play a critical role in Go profiling. So let's try to understand th All Go profilers work by collecting samples of stack trace and putting them into [pprof profiles](./pprof.md). Ignoring some details, a pprof profile is just a frequency table of stack traces like shown below: -| stack trace | samples/count | -| ------------ | ------------- | -| main;foo | 5 | -| main;foo;bar | 3 | -| main;foobar | 4 | +| stack trace | count | +| ------------ | ----- | +| main;foo | 5 | +| main;foo;bar | 3 | +| main;foobar | 4 | Let's zoom in on the second stack trace in the table above: `main;foo;bar`. A Go developer will usually be more familiar with seeing a stack trace like this as rendered by `panic()` or [`runtime.Stack()`](https://golang.org/pkg/runtime/#Stack) shown below: