[DevTools] Capture call stacks for svg parser console messages.

[DevTools] Capture call stacks for svg parser console messages.

We collect call stacks synchronously a bit later in ConsoleMessageStorage::reportMessage,
so there is no performance penalty.

BUG=611926
Committed: https://crrev.com/8619d40f39c2e182d1042db6aa24a4dc95d388f1
Cr-Commit-Position: refs/heads/master@{#394702}

[dgozman, 2016-05-18 23:16:09]

The CQ bit was checked by dgozman@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-05-18 23:16:31]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1992663003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1992663003/1

[dgozman, 2016-05-19 00:20:15]

The CQ bit was unchecked by dgozman@chromium.org

[dgozman, 2016-05-19 02:22:00]

dgozman@chromium.org changed reviewers:
+ kozyatinskiy@chromium.org, pfeldman@chromium.org

[dgozman, 2016-05-19 02:22:02]

Take a look please.

[kozy, 2016-05-19 06:51:41]

The CQ bit was checked by kozyatinskiy@chromium.org

[kozy, 2016-05-19 06:51:42]

lgtm

[commit-bot: I haz the power, 2016-05-19 06:52:09]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1992663003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1992663003/1

[commit-bot: I haz the power, 2016-05-19 06:57:07]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-19 06:59:52]

Description was changed from

==========
[DevTools] Capture call stacks for svg parser console messages.

We collect call stacks synchronously a bit later in
ConsoleMessageStorage::reportMessage,
so there is no performance penalty.

BUG=611926
==========

to

==========
[DevTools] Capture call stacks for svg parser console messages.

We collect call stacks synchronously a bit later in
ConsoleMessageStorage::reportMessage,
so there is no performance penalty.

BUG=611926

Committed: https://crrev.com/8619d40f39c2e182d1042db6aa24a4dc95d388f1
Cr-Commit-Position: refs/heads/master@{#394702}
==========

[commit-bot: I haz the power, 2016-05-19 06:59:54]

Patchset 1 (id:??) landed as
https://crrev.com/8619d40f39c2e182d1042db6aa24a4dc95d388f1
Cr-Commit-Position: refs/heads/master@{#394702}

[pfeldman, 2016-05-19 07:06:07]

>> We collect call stacks synchronously a bit later in
ConsoleMessageStorage::reportMessage, so there is no performance penalty.

if we do it synchronously, why isn't the stack the same?

[dgozman, 2016-05-19 07:16:25]

On 2016/05/19 07:06:07, pfeldman wrote:
> >> We collect call stacks synchronously a bit later in
> ConsoleMessageStorage::reportMessage, so there is no performance penalty.
> 
> if we do it synchronously, why isn't the stack the same?

It is the same. We just didn't report it to ChromeClient before to avoid all
test rebaselines. After a couple of patches terminal output will be the same as
devtools console.
Current situation blocks me from moving console into v8_inspector.