Companion to https://codereview.chromium.org/33973002 Generate correct source locations for Dart lo…

Companion to https://codereview.chromium.org/33973002 Generate correct source locations for Dart log messages.

BUG=
R=vsm@google.com

Committed: https://code.google.com/p/dart/source/detail?r=28976

[Jacob, 2013-10-21 23:22:31]

https://codereview.chromium.org/33993002/diff/1/tools/dom/scripts/systemnativ...
File tools/dom/scripts/systemnative.py (left):

https://codereview.chromium.org/33993002/diff/1/tools/dom/scripts/systemnativ...
tools/dom/scripts/systemnative.py:919: '        if (!scriptCallStack->size())\n'
it was a bug we ever generated this code.  As this method is now expensive as we
actually implement it, we shouldn't be calling it when not needed.

[vsm, 2013-10-22 00:32:59]

lgtm

https://chromiumcodereview.appspot.com/33993002/diff/1/tools/dom/src/native_D...
File tools/dom/src/native_DOMImplementation.dart (right):

https://chromiumcodereview.appspot.com/33993002/diff/1/tools/dom/src/native_D...
tools/dom/src/native_DOMImplementation.dart:84: // Throwing an exception is the
only way to generate a stack trace.
Is there a bug to file for this?

[Jacob, 2013-10-22 00:45:37]

https://chromiumcodereview.appspot.com/33993002/diff/1/tools/dom/src/native_D...
File tools/dom/src/native_DOMImplementation.dart (right):

https://chromiumcodereview.appspot.com/33993002/diff/1/tools/dom/src/native_D...
tools/dom/src/native_DOMImplementation.dart:84: // Throwing an exception is the
only way to generate a stack trace.
On 2013/10/22 00:32:59, vsm wrote:
> Is there a bug to file for this?

https://code.google.com/p/dart/issues/detail?id=2573

It looks like the general conclusion of the DartVM team is to not support it.

[Jacob, 2013-10-22 00:46:34]

Committed patchset #1 manually as r28976 (presubmit successful).