-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#wish #3
Labels
Comments
Thanks for your idea. I will keep this in my to-do list. |
Absolutely. We should start with http://github.com/learnboost/engine.io, which is the core dependency of the upcoming socket.io 1.0. The luvit team already did their engine port. |
The deletes in stream.h for example would cause a leak if the callback throws. |
Thanks. I'll review and fix them soon. |
Closed
kennethho
pushed a commit
to kennethho/node.native
that referenced
this issue
Dec 17, 2012
It's making node.js crash when run as root. Backtrace: (gdb) bt #0 0x00007fff856e3ff9 in __findenv () d5#1 0x00007fff856e404c in getenv () d5#2 0x000000010004c850 in loop_init (loop=0x10045a792, flags=8) at ev.c:1707 d5#3 0x000000010004cb3b in ev_backend [inlined] () at /Users/tjfontaine/Development/node/deps/uv/src/unix/ev/ev.c:2090 d5#4 0x000000010004cb3b in ev_default_loop (flags=1606417108) at ev.c:2092 d5#5 0x000000010004e5c6 in uv__loop_init (loop=0x10066e330, default_loop=1) at loop.c:52 d5#6 0x0000000100044367 in uv_default_loop () at core.c:196 d5#7 0x0000000100004625 in node::Init (argc=1606417456, argv=0x100b0f490) at node.cc:2761 d5#8 0x000000010000797d in node::Start (argc=1606417600, argv=0x0) at node.cc:2888 d5#9 0x0000000100000ca4 in start () This reverts commits: b49d6f7 unix: fix uv_set_process_title() a9f6f06 unix: fix format string vulnerability in freebsd.c a87abc7 unix: avoid buffer overflow in proctitle.c dc97d44 unix: move uv_set_process_title() to proctitle.c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
http://socket.io/ port server for node.native
The text was updated successfully, but these errors were encountered: