[inspector] don't use v8::Isolate::GetCurrent in V8StackTraceImpl

[inspector] don't use v8::Isolate::GetCurrent in V8StackTraceImpl

In inspector code everywhere except V8StackTraceImpl we get pointer to isolate from inspector object or v8::FunctionCallbackInfo. We can avoid usage of v8::Isolate::GetCurrent in V8StackTraceImpl too. It will simplify a little embedder code by removing requirement to have v8::Isolate::Scope before calling to V8InspectorSession::dispatchProtocolMessage.

BUG=v8:5907
R=dgozman@chromium.org

Review-Url: https://codereview.chromium.org/2789593002
Cr-Commit-Position: refs/heads/master@{#44282}
Committed: https://chromium.googlesource.com/v8/v8/+/8adf294cb4700e069f3da27b941417560a68e5f3

[kozy, 2017-03-30 16:17:52]

Dmitry, please take a look.

[kozy, 2017-03-30 18:19:57]

Description was changed from

==========
[inspector] don't use v8::Isolate::Current in V8StackTraceImpl

In inspector code everywhere except V8StackTraceImpl we get pointer to isolate
from inspector object or v8::FunctionCallbackInfo. We can avoid usage of
v8::Isolate::GetCurrent in V8StackTraceImpl too. It will simplify a little
embedder code by removing requirement to have v8::Isolate::Scope before calling
to V8InspectorSession::dispatchProtocolMessage.

BUG=v8:5907
R=dgozman@chromium.org
==========

to

==========
[inspector] don't use v8::Isolate::GetCurrent in V8StackTraceImpl

In inspector code everywhere except V8StackTraceImpl we get pointer to isolate
from inspector object or v8::FunctionCallbackInfo. We can avoid usage of
v8::Isolate::GetCurrent in V8StackTraceImpl too. It will simplify a little
embedder code by removing requirement to have v8::Isolate::Scope before calling
to V8InspectorSession::dispatchProtocolMessage.

BUG=v8:5907
R=dgozman@chromium.org
==========

[dgozman, 2017-03-30 21:10:39]

lgtm

[kozy, 2017-03-30 21:51:00]

The CQ bit was checked by kozyatinskiy@chromium.org

[commit-bot: I haz the power, 2017-03-30 21:51:09]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-30 22:17:26]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490910660909490, "parent_rev":
"114d6b4b87691fcbb3613c5de377d3d6805bf3e2", "commit_rev":
"8adf294cb4700e069f3da27b941417560a68e5f3"}

[commit-bot: I haz the power, 2017-03-30 22:17:36]

Description was changed from

==========
[inspector] don't use v8::Isolate::GetCurrent in V8StackTraceImpl

In inspector code everywhere except V8StackTraceImpl we get pointer to isolate
from inspector object or v8::FunctionCallbackInfo. We can avoid usage of
v8::Isolate::GetCurrent in V8StackTraceImpl too. It will simplify a little
embedder code by removing requirement to have v8::Isolate::Scope before calling
to V8InspectorSession::dispatchProtocolMessage.

BUG=v8:5907
R=dgozman@chromium.org
==========

to

==========
[inspector] don't use v8::Isolate::GetCurrent in V8StackTraceImpl

In inspector code everywhere except V8StackTraceImpl we get pointer to isolate
from inspector object or v8::FunctionCallbackInfo. We can avoid usage of
v8::Isolate::GetCurrent in V8StackTraceImpl too. It will simplify a little
embedder code by removing requirement to have v8::Isolate::Scope before calling
to V8InspectorSession::dispatchProtocolMessage.

BUG=v8:5907
R=dgozman@chromium.org

Review-Url: https://codereview.chromium.org/2789593002
Cr-Commit-Position: refs/heads/master@{#44282}
Committed:
https://chromium.googlesource.com/v8/v8/+/8adf294cb4700e069f3da27b941417560a6...
==========

[commit-bot: I haz the power, 2017-03-30 22:17:36]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/8adf294cb4700e069f3da27b941417560a6...