Cadey Ratio 50c1deaa7d | ||
---|---|---|
.. | ||
.circleci | ||
agent | ||
examples/hello | ||
goprocess | ||
internal | ||
signal | ||
Gopkg.lock | ||
Gopkg.toml | ||
LICENSE | ||
README.md | ||
cmd.go | ||
main.go | ||
main_test.go |
README.md
gops
gops is a command to list and diagnose Go processes currently running on your system.
$ gops
983 uplink-soecks (/usr/local/bin/uplink-soecks)
52697 gops (/Users/jbd/bin/gops)
4132* foops (/Users/jbd/bin/foops)
51130 gocode (/Users/jbd/bin/gocode)
Installation
$ go get -u github.com/google/gops
Diagnostics
For processes that starts the diagnostics agent, gops can report additional information such as the current stack trace, Go version, memory stats, etc.
In order to start the diagnostics agent, see the hello example.
package main
import (
"log"
"time"
"github.com/google/gops/agent"
)
func main() {
if err := agent.Listen(nil); err != nil {
log.Fatal(err)
}
time.Sleep(time.Hour)
}
Manual
It is possible to use gops tool both in local and remote mode.
Local mode requires that you start the target binary as the same user that runs gops binary. To use gops in a remote mode you need to know target's agent address.
In Local mode use process's PID as a target; in Remote mode target is a host:port
combination.
0. Listing all processes running locally
To print all go processes, run gops
without arguments:
$ gops
983 uplink-soecks (/usr/local/bin/uplink-soecks)
52697 gops (/Users/jbd/bin/gops)
4132* foops (/Users/jbd/bin/foops)
51130 gocode (/Users/jbd/bin/gocode)
Note that processes running the agent are marked with *
next to the PID (e.g. 4132*
).
$ gops stack (<pid>|<addr>)
In order to print the current stack trace from a target program, run the following command:
$ gops stack (<pid>|<addr>)
gops stack 85709
goroutine 8 [running]:
runtime/pprof.writeGoroutineStacks(0x13c7bc0, 0xc42000e008, 0xc420ec8520, 0xc420ec8520)
/Users/jbd/go/src/runtime/pprof/pprof.go:603 +0x79
runtime/pprof.writeGoroutine(0x13c7bc0, 0xc42000e008, 0x2, 0xc428f1c048, 0xc420ec8608)
/Users/jbd/go/src/runtime/pprof/pprof.go:592 +0x44
runtime/pprof.(*Profile).WriteTo(0x13eeda0, 0x13c7bc0, 0xc42000e008, 0x2, 0xc42000e008, 0x0)
/Users/jbd/go/src/runtime/pprof/pprof.go:302 +0x3b5
github.com/google/gops/agent.handle(0x13cd560, 0xc42000e008, 0xc420186000, 0x1, 0x1, 0x0, 0x0)
/Users/jbd/src/github.com/google/gops/agent/agent.go:150 +0x1b3
github.com/google/gops/agent.listen()
/Users/jbd/src/github.com/google/gops/agent/agent.go:113 +0x2b2
created by github.com/google/gops/agent.Listen
/Users/jbd/src/github.com/google/gops/agent/agent.go:94 +0x480
# ...
$ gops memstats (<pid>|<addr>)
To print the current memory stats, run the following command:
$ gops memstats (<pid>|<addr>)
$ gops gc (<pid>|<addr>)
If you want to force run garbage collection on the target program, run gc
.
It will block until the GC is completed.
$ gops version (<pid>|<addr>)
gops reports the Go version the target program is built with, if you run the following:
$ gops version (<pid>|<addr>)
devel +6a3c6c0 Sat Jan 14 05:57:07 2017 +0000
$ gops stats (<pid>|<addr>)
To print the runtime statistics such as number of goroutines and GOMAXPROCS
.
Profiling
Pprof
gops supports CPU and heap pprof profiles. After reading either heap or CPU profile,
it shells out to the go tool pprof
and let you interatively examine the profiles.
To enter the CPU profile, run:
$ gops pprof-cpu (<pid>|<addr>)
To enter the heap profile, run:
$ gops pprof-heap (<pid>|<addr>)
Execution trace
gops allows you to start the runtime tracer for 5 seconds and examine the results.
$ gops trace (<pid>|<addr>)