go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added section about attaching debugger

This commit is contained in:
Fabricio Voznika 2019-07-29 18:35:27 -07:00 committed by Ian Lewis
parent 46ee8873ff
commit 6ee109aca4
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
content/docs/user_guide/debugging.md
View File

@ -56,6 +56,30 @@ sudo runsc --root /var/run/docker/runtime-runsc/moby debug --stacks 63254c6ab3a6
> `/var/run/docker/runtime-[runtime-name]/moby`. If in doubt, `--root` is logged to
> `runsc` logs.
## Debugger
You can debug gVisor like any other Golang program. If you're running with Docker,
you'll need to find the sandbox PID and attach the debugger as root. Other than
that, it's business as usual.
```bash
# Start the container you want to debug.
docker run --runtime=runsc --rm --name=test -d alpine sleep 1000
# Find the sandbox PID.
docker inspect test | grep Pid | head -n 1
# Attach your favorite debugger.
sudo dlv attach <PID>
# Set a breakpoint and resume.
break mm.MemoryManager.MMap
continue
```
> Note: if the debugger cannot find symbols, rebuild runsc in debug mode:
> `bazel build -c dbg //runsc:runsc`
## Profiling
`runsc` integrates with Go profiling tools and gives you easy commands to profile