I suspect the reason you don't get the full stack trace is that you call PrintCurrentStackTrace after the stack has been unwound. If you use V8::AddMessageListener to add a message callback you will get a callback before the stack is unwound and PrintCurrentStackTrace should give you the full stack.
This is not a pretty solution though. The "proper" way to do this would be to capture the stack trace in the message object at the point when the exception is thrown and then printing it when the vm has bailed out and returned to your code. We had an implementation of that but there were some problems with it so I disabled it. Eventually we should finish that and reenable that so you don't need to use AddMessageListener. -- Christian On Mon, Jun 8, 2009 at 6:17 PM, ryan dahl<[email protected]> wrote: > >> Any guidance from the V8 dev team ? > > I'm also interested in this problem. > > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
