Listen on unix socket in debugger #5059

Activity

1. Fishrock123

   added

   questionIssues asking questions about Node.js.Issues asking questions about Node.js.

   debugger

   on Feb 3, 2016
2. mscdex

   added

   feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.

   and removed

   questionIssues asking questions about Node.js.Issues asking questions about Node.js.

   on Feb 3, 2016
3. 3y3

   changed the title [-][debugger][feature] listen on unix socket[/-] [+]Listen on unix socket in debugger[/+] on Feb 3, 2016
4. bnoordhuis commented on Feb 4, 2016

   

   bnoordhuis

   on Feb 4, 2016

   Member

   More actions

   There are no real technical obstacles but what is the use case? Let me rephrase: when is a TCP socket not good enough?
5. 3y3 commented on Feb 5, 2016

   

   3y3

   on Feb 5, 2016

   Author

   More actions

   For example:
   We have remote server with development environment. Server used by some users in one time.
   If we try to start debugger on port 5858, it can cause EADDRINUSE. So we need to find free port to debug our app.
   Instead of this we can start debugger to listen on socket in our home dir and be sure what we can listen on it.
6. bnoordhuis commented on Feb 5, 2016

   

   bnoordhuis

   on Feb 5, 2016

   Member

   More actions

   I have a patch in the works (#5025) that makes --debug-port=0 bind to a random port, would that help? It's perhaps less convenient because you'll need to parse stderr or query process.debugPort. OTOH, you don't get stale socket errors like you do with UNIX sockets.
7. 3y3 commented on Feb 5, 2016

   

   3y3

   on Feb 5, 2016

   Author

   More actions

   --debug-port=0 sounds like a dream. Is this work correctly with child_process?
8. bnoordhuis commented on Feb 5, 2016

   

   bnoordhuis

   on Feb 5, 2016

   Member

   More actions

   Yes, it does.
9. 3y3

   closed this as completedon Feb 5, 2016