You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux P3 6.8.0-59-generic #61~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 15 17:03:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
Unfortunately I am unable to provide a minimal reproduction repository.
I am running my code via VS-Codium's native debugging (launch.json) and on recent versions I receive Segmentation fault (core dumped). When I execute the same command (the console output of the command VS-Codium runs, but without VS-Codium attaching its native debugger to node) on command line the application executes as expected.
I am also using the n npm package to change node versions, so it is possible this is somehow an issue. That said, when I use n to switch to any version prior to 23.11.0, such as 23.10.0, everything works as expected.
How often does it reproduce? Is there a required condition?
Happens every time.
What is the expected behavior? Why is that the expected behavior?
The application starts as normal, stopping on breakpoints within the code editor as with previous versions.
$ n i 24.0.1
copying : node/24.0.1
installed : v24.0.1 (with npm 11.3.0)
Note: the node command changed location and the old location may be remembered in your current shell.
old : /usr/bin/node
new : /usr/local/bin/node
If "node --version" shows the old version then start a new shell, or reset the location hash with:
hash -r (for bash, zsh, ash, dash, and ksh)
rehash (for csh and tcsh)
The text was updated successfully, but these errors were encountered:
Version
v23.11.0, v24.0.0, v24.0.1
Platform
Subsystem
No response
What steps will reproduce the bug?
Unfortunately I am unable to provide a minimal reproduction repository.
I am running my code via VS-Codium's native debugging (launch.json) and on recent versions I receive
Segmentation fault (core dumped)
. When I execute the same command (the console output of the command VS-Codium runs, but without VS-Codium attaching its native debugger to node) on command line the application executes as expected.The command VS-Codium executes is the following;
I am also using the
n
npm package to change node versions, so it is possible this is somehow an issue. That said, when I usen
to switch to any version prior to23.11.0
, such as23.10.0
, everything works as expected.How often does it reproduce? Is there a required condition?
Happens every time.
What is the expected behavior? Why is that the expected behavior?
The application starts as normal, stopping on breakpoints within the code editor as with previous versions.
What do you see instead?
Additional information
Output of
find node_modules -iname *.node
Output of
which node
Output of
node --version
A possible red-herring, but could be related;
The text was updated successfully, but these errors were encountered: