Skip to content
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

usage assistance #1

Open
cdaringe opened this issue Apr 28, 2016 · 2 comments
Open

usage assistance #1

cdaringe opened this issue Apr 28, 2016 · 2 comments

Comments

@cdaringe
Copy link

hello:

i'd be happy to contribute back to your docs if you can lend some tips. my program fires up at min 3 child_processes

node --debug index.js

  1. --debug doesn't stop on my debuggers. node debug ... does, but not --debug
  2. how do i attach via the cli (if even feasible) to other processes? that is, i clearly see my new child_processes come up with 5859, 5860, etc etc, but to my knowledge there's no node attach -p 5860 cmd. what's your strategy here?

thanks!

-chris

@jacobq
Copy link

jacobq commented Jul 10, 2018

I realize this is an old thread but thought you might want to check out this updated post: Debugging Node.js with Chrome DevTools. You can use Chrome DevTools to attach to node processes. The tricky part (for me at least) is figuring out how to make 3rd party modules that call spawn use child-process-debug instead (or otherwise get the --debug / --inspect flag passed to them).

@ccckblaze
Copy link

#4
hope this helps @cdaringe

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

No branches or pull requests

3 participants