On 2014/06/05 09:11:20, yurys wrote:
Yang, could you do OWNER review?
Now that I looked closer at this API, I see (if I'm not mistaken) two ways
to
get the script name of where the exception was thrown:
- Through the script in the Message object, like exposed in this CL.
- Through the stack trace in the Message object. The top most function in
the
stack trace can be used for Function::GetScriptOrigin, which gives you a
ScriptOrigin object, containing the script name or URL.
I wonder if we even need the first option. If not, we could even rip out the
script from the Message object altogether and just always use the second
option
to get to the script.
https://codereview.chromium.org/265593002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
