2017-10-16 8:54 GMT+02:00 Pirate Praveen <prav...@onenetbeyond.org>:
> On 10/16/2017 10:32 AM, Pirate Praveen wrote:
> > I don't think any of them is a C++ addon, probably one of their
> > dependencies.
> >
> >
> >
>
> After using segfault-handler node module, I get this message,
>
> PID 21070 received SIGSEGV for address: 0x0
> /usr/local/lib/node_modules/segfault-handler/build/
> Release/segfault-handler.node(+0x1a0d)[0x7f54aad48a0d]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f54ad5140c0]
> [0x368109d6c128]
>
> npm install -g segfault-handler
>
> and add export NODE_PATH=/usr/local/lib/node_modules in debian/rules
>
> and add these two lines to /usr/lib/nodejs/webpack/bin/webpack.js
>
> var SegfaultHandler = require('segfault-handler');
>
> SegfaultHandler.registerHandler("crash.log");
>
You could get a more useful stack trace by installing nodejs-dbgsym package
from
deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main
Jérémy
