This module is a critical tool for debugging Node.js C/C++ native code modules, and is safe to use in production environments. Normally, when a bug is triggered in native code, the node process simply ends with no helpful information. In production, this can manifest as worker processes restarting for seemingly no reason. Running node in gdb is messy and infeasible for a production environment. Instead this module will sit unobtrusively doing nothing (zero perf impact) as long as Node is well-behaved. If a SIGSEGV signal is raised, the module will print a native stack trace to both STDERR and to a timestamped file (STDERR is usually ignored in production environments. files are better).
Using the module is as simple as:
var segvhandler = require('segfault-handler'); segvhandler.registerHandler(); segvhandler.causeSegfault(); // simulates a buggy native module that dereferences NULL
Obviously, you would only include the first two lines in your own code; the third is for testing purposes and to demonstrate functionality.
After running the above sample, you will see a stacktrace that looks like:
PID 67926 received SIGSEGV for address: 0x0 0 segvhandler_native.node 0x00000001007e83d6 _ZL16segfault_handleriP9__siginfoPv + 235 1 libSystem.B.dylib 0x00007fff844d11ba _sigtramp + 26 2 ??? 0x00007fff5fc404a0 0x0 + 140734800069792 3 segvhandler_native.node 0x00000001007e80fd _Z22segfault_stack_frame_2v + 9 4 segvhandler_native.node 0x00000001007e82d4 _Z13CauseSegfaultRKN2v89ArgumentsE + 17 5 node 0x00000001000a45de _ZN2v88internalL21Builtin_HandleApiCallENS0_12_GLOBAL__N_116BuiltinArgumentsILNS0_21BuiltinExtraArgumentsE1EEEPNS0_7IsolateE + 430
Now you can start debugging using tools like "objdump -dS module.node" to try and sort out what the stack actually means. Sometimes, just identifying which native module is causing problems is the biggest win.
Cheers, enjoy. And happy hunting.