Comments (5)
Weird that looks like npm can't find [email protected] but that is the latest version.
Can you npm -v
and put the output here to be sure you are on a version that support the ^
operator?
Thanks
from node-segfault-handler.
[xxx@sv]:<~>$ npm -v
1.2.30
from node-segfault-handler.
wow Last commit there was from 2 years ago!
https://github.com/npm/npm/tree/v1.2.30
If you run node -v
and the version is less than v0,10 I strongly suggest that you upgrade that too.
If you are v0.10 or above then upgrade npm
npm install -g npm
as instructed here
Can I ask where you got this install of node and npm from?
from node-segfault-handler.
On some shared shell hosting.
I use node v0.8.x because of module db-mysql. With v0.10 you can't install it. So I'm in node 0.8. And benchmarks says that 0.8 is better for sending UTF8 data, this is the second reason.
http://nodejs.org/benchmarks-v0.10-vs-v0.8/
If the reason of SIGSEGV will be in db-mysql (and this is the only native module I use) then probably I will change node to v0.10.
Anyway, thanks! :) EDIT, Now is another thing:
[xxx@sv]:<>$ npm -v>$ npm install segfault-handler
2.4.1
Naruszenie ochrony pamięci (zrzut pamięci)
[xxx@sv]:<
[email protected] install /usr/home/xxx/node_modules/segfault-handler
node-gyp rebuild
gmake: Wejście do katalogu '/usr/home/xxx/node_modules/segfault-handler/build'
CXX(target) Release/obj.target/segfault-handler/src/segfault-handler.o
gmake: g++: Polecenie nie znalezione
segfault-handler.target.mk:80: polecenia dla obiektu 'Release/obj.target/segfault-handler/src/segfault-handler.o' nie powiodły się
gmake: *** [Release/obj.target/segfault-handler/src/segfault-handler.o] Błąd 127
gmake: Opuszczenie katalogu '/usr/home/xxx/node_modules/segfault-handler/build'
gyp ERR! build error
gyp ERR! stack Error: gmake
failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/home/xxx/.nvm/v0.8.25/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:99:17)
gyp ERR! stack at Process._handle.onexit (child_process.js:686:10)
gyp ERR! System FreeBSD 10.1-RELEASE
gyp ERR! command "node" "/usr/home/xxx/.nvm/v0.8.25/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/home/xxx/node_modules/segfault-handler
gyp ERR! node -v v0.8.25
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
npm ERR! FreeBSD 10.1-RELEASE
npm ERR! argv "node" "/home/xxx/.nvm/v0.8.25/bin/npm" "install" "segfault-handler"
npm ERR! node v0.8.25
npm ERR! npm v2.4.1
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the segfault-handler package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls segfault-handler
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /usr/home/xxx/npm-debug.log
from node-segfault-handler.
@Kamil93 OK So I am running FreeBSD 11 CURRENT
node 4.4.2
npm 2.1.4
and this is no longer an issue so I am going to close it
Please re-open if you think there is an issue with FreeBSD support.
from node-segfault-handler.
Related Issues (20)
- SIGSEGV in 0.0.64 HOT 1
- Handler segfaults itself when using multiple v8 isolates
- Node 10 Compatibility HOT 2
- Failing to run on Alpine Linux HOT 2
- registerHandler is not a function in Ubuntu 14.04 LTS
- Side effects on native dependencies on Windows HOT 1
- question: requiring this module fixes my segfault problem. What am I doing? :-D HOT 1
- Please clean build output [cosmetic]
- Fails to build under Node 12 HOT 6
- Node 13.x uses SIGSEGV, new API available HOT 1
- Electron 7.x.x and > throws context aware warning HOT 1
- Out of the box build failure -- `'v8-debug.h' file not found` HOT 3
- Missing "execinfo.h" on Node Alpine HOT 7
- Possible to unregister at runtime?
- invalid ELF header
- Segfault handler should abort, or have the option to abort
- Crash log only contains SIGSEGV and /lib/libc.so.6 HOT 2
- Error when building on electron HOT 2
- ...
- Error building on Node 16.19.0
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-segfault-handler.