Thanks Darshit!
In my program I am not catching uncaught exceptions with process.on, so
this is not the point. I think Jimb's observation explains the empty stack.
Il giorno sabato 17 gennaio 2015 07:16:32 UTC+1, Darshit Shah ha scritto:
>
> In my program also I have handled all uncaught exceptions using
> process.on('uncaughtException'). And I was unable to get any stack trace
> for exception got in this function. So to debug that problem, I need to
> comment out process.on portion of the code and then proper stack trace was
> printed on screen.
>
> Hope that helps.
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/0e1cb7b7-d4ab-4615-b294-4f67f2a8c692%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
