node-segfault-handler
node-segfault-handler copied to clipboard
ddopson
Tool for debugging native Node.js modules and getting stack traces when things go wrong.
| Key | Value | |---|---| | Edition | Windows 11 Pro | | Version | 22H2 | | OS build | 22621.1992 | | Experience | Windows Feature Experience...
* **Node.js Version**: 15.8.0 * **OS**: linux - debian * **Scope**: runtime i am getting this error ``Segmentation fault`` i don't know why or where ```js PID 22564 received SIGSEGV...
Hi there, we are running an old version of node and attempting to run on WSL2. I am new to WSL2 and wondering if there is support for this v-environment?...
I've had an issue building the segfault-handler node module with npm since upgrading to node 16.19.0. It seems like there's a missing dependency: `127 error /Users/****/Library/Caches/node-gyp/16.19.0/include/node/v8.h:22:10: fatal error: atomic: No...
With certain versions of NodeJS, we are encountering errors when rebuilding this dependency using `electron-builder`: It works in Node 16.3 Does not work in Node 16.16: ``` • electron-builder version=22.11.7...
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...
The crash callback doesn't do anything with the returned value so this should be `void` to indicate that.
``` SegfaultHandler.registerHandler('crash.log', function(signal, address, stack) { console.log('here!') }) SegfaultHandler.causeSegfault() ``` `here!` is never printed. A bug or am I doing something wrong?
The alpine fix broke thw Windows build. This works for both.
Hi there, Am I doing something wrong? or it's a known issue? I've the following code: ``` SegfaultHandler.registerHandler("crash.log", function(signal, address, stack) { console.log('TETETETETETETETET'); }); SegfaultHandler.causeSegfault(); ``` I've never seen my...
