How to interpret Go stacktrace
<p>I am getting this stacktrace when running a go program:</p>

<pre><code>        /home/travis/.gimme/versions/go1.6.linux.amd64/src/runtime/panic.go:464 +0x3e6
github.com/DataDog/datadog-go/statsd.(*Client).Event(0x0, 0xc8200c7ec8, 0x0, 0x0)
        /home/travis/gopath/src/github.com/DataDog/datadog-go/statsd/statsd.go:286 +0x11f
github.com/some/path/server.(*Server).buildAndUpdate(0xc820024068, 0xc820064600, 0x0, 0x0)
        /home/travis/gopath/src/github.com/some/path/server/http.go:86 +0xf9f
created by github.com/some/path/server.(*Server).processPullRequestEvent
        /home/travis/gopath/src/github.com/some/path/server/http.go:169 +0x53f
</code></pre>

<p>The signature of the Event function is:</p>

<pre><code>func (c *Client) Event(e *Event) error
</code></pre>

<p>which can also be seen here: <a href="https://github.com/DataDog/datadog-go/blob/cc2f4770f4d61871e19bfee967bc767fe730b0d9/statsd/statsd.go#L285" rel="noreferrer">https://github.com/DataDog/datadog-go/blob/cc2f4770f4d61871e19bfee967bc767fe730b0d9/statsd/statsd.go#L285</a></p>

<p>The type definition for <code>Event</code> can be seen here: <a href="https://github.com/DataDog/datadog-go/blob/cc2f4770f4d61871e19bfee967bc767fe730b0d9/statsd/statsd.go#L333" rel="noreferrer">https://github.com/DataDog/datadog-go/blob/cc2f4770f4d61871e19bfee967bc767fe730b0d9/statsd/statsd.go#L333</a></p>

<p>The type definition for <code>Client</code> can be seen here: <a href="https://github.com/DataDog/datadog-go/blob/cc2f4770f4d61871e19bfee967bc767fe730b0d9/statsd/statsd.go#L59" rel="noreferrer">https://github.com/DataDog/datadog-go/blob/cc2f4770f4d61871e19bfee967bc767fe730b0d9/statsd/statsd.go#L59</a></p>

<p>My question is, how do I interpret the memory addresses on this line, and more generally, any stack traces which involve typed variables as targets and as arguments?</p>

<pre><code>github.com/DataDog/datadog-go/statsd.(*Client).Event(0x0, 0xc8200c7ec8, 0x0, 0x0)
</code></pre>

<p>When I looked at <a href="http://www.goinggo.net/2015/01/stack-traces-in-go.html" rel="noreferrer">http://www.goinggo.net/2015/01/stack-traces-in-go.html</a> (which is the only information I was able to find on the subject), I didn't see anything about how to interpret the output when structs were involved.</p>