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

tools/dom/src/native_DOMImplementation.dart

Index: tools/dom/src/native_DOMImplementation.dart
diff --git a/tools/dom/src/native_DOMImplementation.dart b/tools/dom/src/native_DOMImplementation.dart
index e650c6fd0c5c0aef41f0256b35e434d6420ea27e..f6c9e499177f8aede91d38478ab22dc78ab85b98 100644
--- a/tools/dom/src/native_DOMImplementation.dart
+++ b/tools/dom/src/native_DOMImplementation.dart
@@ -79,6 +79,15 @@ class _Utils {
     return result;
   }
 
+  static List captureParsedStackTrace() {
+    try {
+      // Throwing an exception is the only way to generate a stack trace.

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

Is there a bug to file for this?

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

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.

+      throw new Exception();
+    } catch (e, stackTrace) {
+      return parseStackTrace(stackTrace);
+    }
+  }
+
   static void populateMap(Map result, List list) {
     for (int i = 0; i < list.length; i += 2) {
       result[list[i]] = list[i + 1];