node.js is extremely hard to debug, one method I found is - binary search - cut app in half and see in which half the problem is - and continue cutting in half until you found the source :).
On Wednesday, September 18, 2013 3:21:04 PM UTC+4, Vivek Goel wrote: > > Hi, > I have node daemon (gearman worker). Sometime I am facing the problem that > the process don't respond to some particular requests (gearman jobs). > > I am using following modules > > - gearman > - mysql > - redis > - aws sdk > - node-gcm > - node-apn > > I don't know in which module the program is hanging. Is it hanging in my > code or some of third party code. > > Is there a way to find out in which module it is hanged (while process is > in running state) ? > > > What are the methods used for debugging already running process in node ? > > > > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
