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 On Fri, Jul 24, 2009 at 4:47 PM, Dean McNamee<[email protected]> wrote: > > Christian committed a change to enable stack traces on exception > object. See bleeding edge r2338 and r2302. > > Good luck > -- dean > > On Fri, Jul 24, 2009 at 4:41 PM, ryan dahl<[email protected]> wrote: >> >> 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? >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
