blob: 05539f66586194cd94f772d182dcaee86c65cb71 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
{ lib
, buildGoModule
, fetchFromGitHub
}:
buildGoModule rec {
pname = "pprof";
version = "unstable-2023-07-05";
src = fetchFromGitHub {
owner = "google";
repo = "pprof";
rev = "200ffdc848b879f8aff937ffeba601c186916257";
hash = "sha256-/Y1Tj9z+2MNe+b2vzd4F+PwHGSbCYP7HpbaDUL9ZzKQ=";
};
vendorHash = "sha256-MuejFoK49VMmLt7xsiX/4Av7TijPwM9/mewXlfdufd8=";
meta = with lib; {
description = "A tool for visualization and analysis of profiling data";
homepage = "https://github.com/google/pprof";
license = licenses.asl20;
longDescription = ''
pprof reads a collection of profiling samples in profile.proto format and
generates reports to visualize and help analyze the data. It can generate
both text and graphical reports (through the use of the dot visualization
package).
profile.proto is a protocol buffer that describes a set of callstacks and
symbolization information. A common usage is to represent a set of sampled
callstacks from statistical profiling. The format is described on the
proto/profile.proto file. For details on protocol buffers, see
https://developers.google.com/protocol-buffers
Profiles can be read from a local file, or over http. Multiple profiles of
the same type can be aggregated or compared.
If the profile samples contain machine addresses, pprof can symbolize them
through the use of the native binutils tools (addr2line and nm).
This is not an official Google product.
'';
};
}
|