But then, you will have to correctly parse it to get useful information.
It's not much, but parsing still cost some processing time. Not to mention
the amount of information you get is less than using native CallSite
object. The situation I am in is not just only for simple manual on-screen
debugging, but also getting as much as possible info out for some other
personal purposes without incurring much performance penalty. Why letting
V8 stringify it and then we have to parse it later to get even less amount
of data than before the stringify while we could prevent all that from
happening in the first place?
On Thursday, November 13, 2014 2:10:42 AM UTC+7, Axel Kittenberger wrote:
>
> Maybe I miss something, but so I always just did:
>
> "(new Error()).stack.split('\n');"
>
> to get a backtrace, when needed for debugging.
>
> Futher autmatic string processing if needed. These stacktraces from a
> pseudo Error are correct for me in the original example.
>
--
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/8ee99721-1bc8-4ed3-a4da-ff8abf5dbc03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
