Segmentation error when running node in libpthread.so
I was writing a daemon in node (hosted
) and notice that the worker process sometimes accidentally dies. I've added a segault handler to see what's going on, but the typical stacktrace ... useless?
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]
Once I got this trail on error, instead:
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]
which still shows the top call at
(although preceded by the call at node).
I find it hard to believe that a segfault is happening in
(or ... anywhere?), But what is it? Has anyone had this experience in the past? Anyone have any hints for further debugging?
I am on CentOS 6.5 with node v0.10.29 (from epel repository), for reference.
source to share
No one has answered this question yet
Check out similar questions: