title: Segmentation fault while running node in libpthread.so
body: <p>I've been writing a daemon in node (hosted by <a href="https://github.com/nodejitsu/forever" rel="noreferrer"><code>forever</code></a>) and notice that the worker process sometimes randomly dies. I added a <a href="https://www.npmjs.org/package/segfault-handler" rel="noreferrer">segault handler</a> to see what's up, but the typical stacktrace is... unhelpful?</p>
  
  <pre><code>PID 9949 received SIGSEGV for address: 0x0
  /home/wesley/app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0xf60)[0x7f11dd3d8f60]
  /lib64/libpthread.so.0[0x354760f710]
  [0x3d3c10b0d799]
  </code></pre>
  
  <p><em>Once</em> I received this trace on failure, instead:</p>
  
  <pre><code>PID 5820 received SIGSEGV for address: 0x18
  /home/wesley/app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0xf60)[0x7fdfab749f60]
  /lib64/libpthread.so.0[0x354760f710]
  /usr/bin/node(_ZN4node6Buffer14MakeFastBufferERKN2v89ArgumentsE+0x168)[0x426778]
  [0x1d06e36ccdfb]
  </code></pre>
  
  <p>Which <em>still</em> shows the top call in <code>libpthread.so</code> (Though preceded by a call in node proper.)</p>
  
  <p>I find it difficult to believe that the segfault originates in <code>libpthread.so</code> (or... nowhere?), but that's what it looks like? Has anyone had any experiences like this in the past? Does anyone have any tips for further debugging?</p>
  
  <p>I'm running on CentOS 6.5 with node v0.10.29 (from the epel repository), for reference.</p>