On Tue, Jan 22, 2013 at 12:43 PM, Michael <[email protected]> wrote: > I did it 3 times, always the same result: > > Starting program: /usr/local/bin/node index.js > [Thread debugging using libthread_db enabled] > [New Thread 0x7ffff7fef700 (LWP 31807)] > WARNING: ev_io is deprecated, use uv_poll_t > WARNING: ev_timer is deprecated, use uv_timer_t > [New Thread 0x7ffff6f17700 (LWP 31808)] > [New Thread 0x7fffeffff700 (LWP 31809)] > [New Thread 0x7fffeffbe700 (LWP 31810)] > node: ../deps/uv/src/uv-common.h:101: uv__req_unregister: Assertion > `uv__has_active_reqs(loop)' failed. > > Program received signal SIGABRT, Aborted. > 0x0000003c146328a5 in raise () from /lib64/libc.so.6 > Missing separate debuginfos, use: debuginfo-install nodejs-0.8.17-1.x86_64 > (gdb) backtrace full > #0 0x0000003c146328a5 in raise () from /lib64/libc.so.6 > No symbol table info available. > #1 0x0000003c14634085 in abort () from /lib64/libc.so.6 > No symbol table info available. > #2 0x0000003c1462ba1e in __assert_fail_base () from /lib64/libc.so.6 > No symbol table info available. > #3 0x0000003c1462bae0 in __assert_fail () from /lib64/libc.so.6 > No symbol table info available. > #4 0x00000000005db4ae in uv__after_work () > No symbol table info available. > #5 0x00000000005d14da in eio_finish () > No symbol table info available. > #6 0x00000000005d2b62 in eio_poll () > No symbol table info available. > #7 0x00000000005e3098 in uv_eio_want_poll_notifier_cb () > No symbol table info available. > #8 0x00000000005d0039 in uv__async_io () > No symbol table info available. > #9 0x00000000005d4b74 in ev_invoke_pending () > No symbol table info available. > #10 0x00000000005d086d in uv__run () > No symbol table info available. > #11 0x00000000005d0af0 in uv_run () > No symbol table info available. > #12 0x0000000000589365 in node::Start(int, char**) () > No symbol table info available. > #13 0x0000003c1461ecdd in __libc_start_main () from /lib64/libc.so.6 > No symbol table info available. > #14 0x000000000058136d in _start () > No symbol table info available.
Okay, thanks. Is your script using native add-ons, either directly or indirectly? That is, does `find node_modules/ -name \*.node` find anything? You'll want to exclude them one by one in order to isolate the root cause. Also, is this a node binary from one of the centos or fedora repos? If it is, try compiling from the tarball from nodejs.org and see if the problem persists. Last but not least, you may want to verify if the problem exists with the latest development release, 0.9.7. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
