<!-- Thank you for reporting a possible bug in Node.js. Please fill in as much of the template below as you can. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) Subsystem: if known, please specify the affected core module name If possible, please provide code that demonstrates the problem, keeping it as simple and free of external dependencies as you can. --> * **Version**: * **Platform**: * **Subsystem**: <!-- Please provide more details below this comment. --> #node -v v11.8.0 Aborted (core dumped) #uname -a Linux ubuntu1604 4.19.18-041918-generic #041918.201901261840 SMP Sat Jan 26 18:42:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux All versions of node 11.x and node 10.x give this "Aborted (core dumped)" error.
Activity
gireeshpunathil commentedon Jan 27, 2019
can you please run with
ulimit -c unlimited, collect a dump and either:bt fullto get more context?thanks.
bnoordhuis commentedon Jan 27, 2019
The output of
ldd $(which node)would help too.icebluey commentedon Jan 29, 2019
Thanks.
I found the reason:
node was linked to libnode.so of atom.
ChALkeR commentedon Jan 29, 2019
@icebluey could this be closed now, perhaps? Or is there still anything that needs to be done?
richardlau commentedon Jan 30, 2019
This is/was #22319.
xRiiZu commentedon Jul 19, 2020
Anyone have an idea of what can be wrong??
bnoordhuis commentedon Jul 19, 2020
@xRiiZu Look at the stack trace, report it to better-sqlite3.
prachisrivastava-coupa commentedon Sep 20, 2023
bnoordhuis commentedon Sep 21, 2023
@prachisrivastava-coupa please open a new issue