From 6d587f1d2af38a8bb498d6a0a387948120fd61c6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Sun, 10 Jan 2021 14:32:01 +0100 Subject: [PATCH] code links --- pprof.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pprof.md b/pprof.md index e460a06..e7a663d 100644 --- a/pprof.md +++ b/pprof.md @@ -18,7 +18,9 @@ A pprof file contains a list of **stack traces** called *samples* that have one The profile also includes the **time** (in UTC) that the profile was recorded, and the **duration** of the recording. -Additionally the format allows for **drop/keep** regexes for excluding/including certain stack traces, but it's not clear to me if Go is using those at all. There is also room for a list of **comments**, as well as describing the **periodic** interval at which samples were taken. +Additionally the format allows for **drop/keep** regexes for excluding/including certain stack traces, but they're [not used](https://github.com/golang/go/blob/go1.15.6/src/runtime/pprof/proto.go#L375-L376) by Go. There is also room for a list of **comments** ([not used](https://github.com/golang/go/search?q=tagProfile_Comment) either), as well as describing the **periodic** interval at which samples were taken. + +The code for generating pprof output in Go can be found in: [runtime/pprof/proto.go](https://github.com/golang/go/blob/go1.15.6/src/runtime/pprof/proto.go). ### Decoding