Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Segmentation fault from Node 0.8 #3565

Closed
murvinlai opened this issue Jun 27, 2012 · 4 comments
Closed

Segmentation fault from Node 0.8 #3565

murvinlai opened this issue Jun 27, 2012 · 4 comments

Comments

@murvinlai
Copy link

I wrote the program that was running fine wtih Node 0.6.7

i just updated to NOde.0.8 and updated (reinstall) all NPM pakcages. However, when I run the program, right after start, i will give out "Segmentation fault" without any further details.

@murvinlai
Copy link
Author

By the way, I m running on ubuntu

@murvinlai
Copy link
Author

$ sudo gdb --args node eaSsoRestAPIServer.js
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/local/bin/node...done.
(gdb)
(gdb)
(gdb)
(gdb)
(gdb) run
Starting program: /usr/local/bin/node eaSsoRestAPIServer.js
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff7fed700 (LWP 24371)]
Run ReplicaSet Mongo mongodb://10.100.10.190:27017/ssodatabase,10.100.10.190:27018/ssodatabase
[New Thread 0x7ffff7fdc700 (LWP 24372)]
------- POST -----/connectsdk/auth/rest/userLogin
------- GET -----/connectsdk/auth/rest/autoLogin
------- POST -----/connectsdk/auth/rest/logout
------- POST -----/connectsdk/auth/rest/register
------- GET -----/connectsdk/auth/rest/forgotPassword
------- GET -----/connectsdk/auth/rest/forgotPasswordByOriginId
------- GET -----/connectsdk/account/rest/getUserDetail
------- POST -----/connectsdk/account/rest/verifyEmailByToken

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7001ed8 in ?? () from /lib/libc.so.6
(gdb) ^CQuit
(gdb) bt
#0 0x00007ffff7001ed8 in ?? () from /lib/libc.so.6
#1 0x00000000005fbdc3 in uv__stream_destroy (stream=0xed7ac0) at ../deps/uv/src/unix/stream.c:124
#2 0x00000000005e96b6 in uv__finish_close (loop=0xe7b520) at ../deps/uv/src/unix/core.c:151
#3 uv__run_closing_handles (loop=0xe7b520) at ../deps/uv/src/unix/core.c:181
#4 uv__run (loop=0xe7b520) at ../deps/uv/src/unix/core.c:259
#5 0x00000000005e97f0 in uv_run (loop=0xe7b520) at ../deps/uv/src/unix/core.c:265
#6 0x000000000059e6c5 in node::Start(int, char**) ()
#7 0x00007ffff6ca1c4d in __libc_start_main () from /lib/libc.so.6
#8 0x00000000005949fd in _start ()
(gdb)

@bnoordhuis
Copy link
Member

As discussed on IRC, this is very likely a bug in a native add-on, not in node. Closing.

@murvinlai
Copy link
Author

Very likely is the Mongoose problem.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants