stack traces again

[ryan dahl]

There still seems to be no way to get a stack trace - at least not in
1.2.14. PrintCurrentStackTrace doesn't work either after the exception
has taken place or in a MessageListener callback. It was mentioned
this was disabled for performance reasons - is there a way one could
re-enable it?

[Dean McNamee]

Christian committed a change to enable stack traces on exception
object. See bleeding edge r2338 and r2302.

Good luck
-- dean

[Christian Plesner Hansen]

It wasn't removed for performance reasons, it was because the stack
trace that was produced turned out to be an internal debug one, not
one for external consumption. As Dean mentioned we now have proper
stack traces on exception objects and it's on my schedule to rework
api stack traces using the same mechanism.


-- Christian

[Sébastien Pierre]

Nice, this is was my #1 problem with V8 !

-- Sébastien

Le vendredi 24 juillet 2009 à 19:31 +0200, Christian Plesner Hansen a
écrit :

[Christian Plesner Hansen]

In the absence of a "proper" C++ api to get stack traces you can
actually use the new .stack property from C++ in just a few lines of
code. There's an example of how that could work here:

http://code.google.com/p/ekko/source/browse/trunk/src/main.cc?r=15#17

I expect that once we get around to adding a C++ function for getting
a stack trace it will do essentially the same.


-- Christian

2009/7/31 Sébastien Pierre <sebastie...@gmail.com>: