<p>Are there any tools out there which can do static analysis of a program and point out potential sources of null pointer exceptions? </p>
<hr/>**评论：**<br/><br/>The_Sly_Marbo: <pre><p>I appreciate this doesn't answer your question, but I find that good coding practices prevent nil pointer panics.</p>
<ul>
<li>Where possible, define types that can safely be nil, either by returning an error if nil or using default values.</li>
<li><p>Use stack variables so that the pointer can't be nil. For example, <code>bytes.Buffer</code> uses its pointer receiver, so use it as follows:</p>
<p>var buf bytes.Buffer
_, err := data.WriteTo(&buf)
if err != nil {
return nil, err
}</p>
<p>return &buf, nil</p></li>
</ul></pre>Asdayasman: <pre><p>Prepend each line of code with four spaces</p>
<pre><code>like
so
</code></pre>
<p>Or use backticks <code>to surround an inline section</code>.</p></pre>
