Hello,
I am using this lib to debug a crash that occurs randomly in an application which is running on a raspberry pi with a very barebones unix OS. The crash is very hard to reproduce consistently, the app can run for hours with no problems and will sometimes crash after a few minutes.
Here is the log I get after adding node-segfault-handler:
PID 386 received SIGSEGV for address: 0x3f5e2ca8
/usr/lib/node/prod/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x1b2e)[0xb429bb2e]
/lib/libc.so.6(+0x2a300)[0xb6639300]
I was hoping it would point me in the direction of one of the native modules that the app is using, but the log turns out to be not very helpful ^^
I am a bit out of my depth here, and would appreciate it if someone could help me understand what is going on:
- does this log completely rule out the native modules I am using as the source of the crashes ?
- is the "libc.so.6" in the stack a clue for finding the cause of the crash, or is just a part of the segfault-handler logging mechanism ?
- is there anything I can do to make this log a bit more verbose ?
Thanks
Hello,
I am using this lib to debug a crash that occurs randomly in an application which is running on a raspberry pi with a very barebones unix OS. The crash is very hard to reproduce consistently, the app can run for hours with no problems and will sometimes crash after a few minutes.
Here is the log I get after adding node-segfault-handler:
I was hoping it would point me in the direction of one of the native modules that the app is using, but the log turns out to be not very helpful ^^
I am a bit out of my depth here, and would appreciate it if someone could help me understand what is going on:
Thanks