node-fibers debug unusable in OS X about node-fibers HOT 3 CLOSED

Seems that you can't use the debugger in node with DYLD_FORCE_FLAT_NAMESPACE enabled in OS X:

marcel@marcel $ DYLD_FORCE_FLAT_NAMESPACE=1 node debug test.js
debug> run
connecting...There was an internal error in Node's debugger. Please report this bug.
ECONNREFUSED, Connection refused
Error: ECONNREFUSED, Connection refused
    at Client._onConnect (net.js:600:18)
    at IOWatcher.onWritable [as callback] (net.js:186:12)

You can still debug just fine on Linux. Not really sure what to do about this because I don't know enough about dylib to debug this. You may have luck reporting this as an issue in node since it can be reproduced in the absence of node-fibers.

from node-fibers.

I'm on Debian 6, OS X has nothing to do with it.
The issue does not happen with node without fibers, when I wipe them from my app.

Here is the log. There are no breakpoints or debugger calls in the code.

root@debian6:/var/site/chat# node-fibers debug app.js
debug> run
debugger listening on port 5858
connecting...ok
breakpoint #1 in #.[anonymous](exports=#, require=function require%28path%29 {
return Module._load%28path, self%29;
}, module=#, __filename=/var/site/chat/app.js, __dirname=/var/site/chat), /var/site/chat/app.js:7
var util = require('util');
^
debug> c
debug> 24 Apr 09:00:55 - socket.io ready - accepting connections
node: fibers.cc:504: void init(v8::Handlev8::Object): Assertion `Coroutine::is_local_storage_enabled()' failed.

program terminated
debug>

P.S. The code is at http://javascript.info/chat.zip

from node-fibers.

Ok yeah there are multiple issues here. One is a timing issue in node, the other is a problem with the way environment variables are carried over. I fixed the timing issue in laverdet/node@bdb0615 and I'll look at the env issue soon.

from node-fibers.