On 2009/05/19 12:08:46, Søren Gjesse wrote:
> This is not the way to go, as the contexts exposed through the API are
always
> global contexts. It is the GetEventContext on the Message object which
is in
> error, as it returns a non-global context.

> I think we can remove the GetEventContext from the Message object and
use
> Context::GetCurrent() in the API instead.


As discussed offline we cannot use Context::GetCurrent() as it would
return the debugger context. I've changed implementation of
GetEventContext so that it looks up global context by traversing context
chain that was active right before entering the debugger.

http://codereview.chromium.org/112035

--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to