I've installed the latest Node.js for Windows x64 (0.8.19). When I run it, with or without a script file argument it just exits without an error message.
Things I've tried:
I ran node.exe under JetBrains Webstorm, this reported an exit code of -1073740791
I compiled the source code for 0.8.19 using VS2010, this has the same problem in release but in debug it reports the error: Run-Time Check Failure #2 - Stack around the variable 'buf' was corrupted. Continuing from this in debug allows the program to start up.
I installed node.js on my PC at home which is also Win 7 x64 and that worked fine.
Have others had the same problem?
Related
my webstorm debugger works fine if I simply run, say, my server.js directly in debug mode.
However, when I run an NPM script in debug mode (npm start for instance), I get the following exception:
Process finished with exit code -1073741510 (0xC000013A: interrupted by Ctrl+C)
I use Webstorm WebStorm 2016.1.2
Build #WS-145.971, built on May 1, 2016
JRE: 1.8.0_77-b03 x86
JVM: Java HotSpot(TM) Server VM by Oracle Corporation
My Node version is 5.11.0
I run it Windows 7, my colleague is running Windows 10 with same problem.
Did anyone come across this problem yet?
there could be many reasons for this - here are just some of my thoughts which may be useful to someone:
maybe some problem of the IDE: e.g. in this case caused by old watch variables
try to clear the ide/debugger state: e.g. delete breakpoints, watches, etc.
try: Invalidate caches / Restart
maybe just an early exit
I had one case in our node-tests, where some part of the code just called process.exit(0) before the async test-function had finished. This also caused the (confusing) console output:
Process finished with exit code -1073741510 (0xC000013A: interrupted by Ctrl+C)
When I use visual studio code to debug a nodejs app.
visual studio code tell me request 'launch': cannot launch target (reason: spawn node ENOENT)
My nodejs version is 4.2.4
Managed to get past this when running on Windows by specifying npm.cmd instead of npm in the VS code debug configuration like so
"runtimeExecutable": "npm.cmd",
Some discussions are posted in this here
How do I debug "Error: spawn ENOENT" on node.js?
Especially, the following points should be checked
Ensure the environment variable PATH is set
PATHEXT environment variable that can cause certain calls to spawn to not work on Windows.
I was getting this error on a Debian Linux system. I noticed the same thing worked OK on Windows.
Next I noticed that the Node.JS executable is called node on Windows but on Debian (and on Debian-based systems such as Ubuntu) it's called nodejs. So I created an alias - from a root terminal, I ran
ln -s /usr/bin/nodejs /usr/local/bin/node
and this solved the problem.
This usually happens if you already had your Visual Code Editor running while installing node js on Windows OS. I would advise you to shut down your Visual Studio Code and restart it. This problem should go away.
If not do a machine reboot and verify if the debug works flawlessly
I have installed www.deployd.com on my Windows-XP PC for learning purposes. The book am studying ask me to execute the following command at the prompt ::
> dpd create sportsstore
but i get the following error message
Node.exe is not a valid Win32 Application
What must i do to rectify this error?
Thanks.
UPDATE
The node.exe it is complaining about is inside the the tools folder of Deployd. It is like this
C:\program files\Deployd\tools\Node.exe is not a valid Win32 Application
That error is usually an indicator of trying to run a 64bit application in a 32bit OS.
The solution is to change the version of node to the 32bit version. Be careful to choose the same version as your tutorial to avoid any conflicts.
I'm trying to create a simple (software) driver using these instructions.
Host is Windows 7 x64 with fully updated MSVS Express 2013.
Latest windows driver kit is installed and working fine.
A virtual machine also with Windows 7 x64 is succesfully provisioned by VS, and configured exactly following these instructions.
The deployment process seems to execute properly and the build log shows something like:
1> Catalog generation complete.
1> <snip>\Win7Debug\Driver Package\driver.cat
1> Done Adding Additional Store
1> Successfully signed: <snip>\Win7Debug\Driver Package\driver.cat
1>
1> Deploying driver files for project "<snip>\Driver Package\Driver Package.vcxproj". Deployment may take a few minutes...
2>------ Deploy started: Project: Driver, Configuration: Win7 Debug Win32 ------
2> Done Adding Additional Store
2> Successfully signed: <snip>\Win7Debug\Driver.sys
2>
3>------ Deploy started: Project: Driver Package, Configuration: Win7 Debug Win32 ------
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 2 succeeded, 0 failed, 0 skipped ==========
However, when Visual Studio tries to start a debug session, I receive the following error message:
Unfortunately, there's no mention of which file it can't find. I've tried attaching a debugger and hooking kernel32's MessageBox so that maybe I could check the call trace / see which file it is looking for, but VS doesn't like me attaching ollydbg and it brings up a whole lot of other issues.
I've also tried Process Monitor to see what file it is trying to access but it's pretty hard to wade through everything it is doing.
Am I missing something? Anyone can point me in the right direction?
edit1: Did a clean install of both the host as target machine. Followed instructions perfectly: exact same error. Has nobody come across this before?
So the answer is that Visual Studio defaults to Kernel Debugger rather than Remote Debugger. Changing this at least got it to deploy and install the driver, but still caused the build process to hang forever.
I've given up on trying to write a KMDF driver and will instead opt for a global hook via SetWindowsHookEx instead. Not something I preferred, but the process for writing a kernel mode driver in Windows is way too tedious in my eyes.
Hi for responsive images i downloaded project from
https://github.com/andismith/grunt-responsive-images
i installed all those things what they have mentioned...
whenever i say grunt it saying fallowing error:
Running "jshint:all" (jshint) task
>> 3 files lint free.
Running "clean:tests" (clean) task
Cleaning "tmp"...OK
Running "responsive_images:default_options" (responsive_images) task
Fatal error: spawn ENOENT
why i am getting this error pla tellme...
Thnk you.
It is likely because you don't have imagemagick installed: http://www.imagemagick.org/script/index.php
See the FAQ on that plugin: https://github.com/andismith/grunt-responsive-images#faq
I experienced exactly the same error as you yesterday, and I found that I had installed wrong version of node.js eventually.
I'm using 64-bit Windows,but I had installed 32bit version Node.js.
I could install it and it seems working normally, but when I tried to compile existing project, the error message had been shown.
But after I re-install 64-bit version of Node.js, all error had been solved.
If you are using 64bit OS, better to check the version is correct or not.