When investigating an unrelated bug, I noticed we are missing an activation in the stact trace.
The "DivElement.DivElement" is called when initializing "_div" in _ScheduleImmediateHelper.
I expected to see the following activtion:
    "_ScheduleImmediateHelper._ScheduleImmediateHelper"
in the stack trace.

Regards,
   Lars

In the following standalone program:

class B {
  B() { throw 0; }
}

class A {
  final b = new B();
  A();
}

final fisk = new A();

main() {
  print(fisk);
}

the Dart VM seems to display the right information:

0

­0 B.B (file:///usr/local/google/home/bak/stack.dart:3:9)

­1 A.A (file:///usr/local/google/home/bak/stack.dart:7:17)

­2 fisk (file:///usr/local/google/home/bak/stack.dart:11:14)

­3 main (file:///usr/local/google/home/bak/stack.dart:14:9)

­4 _startIsolate.isolateStartHandler (dart:isolate-patch/isolate_patch.dart:216)

­5 _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:124)

////////////////////////////////////////////////////////////////////////////////////
Editor: 1.5.0.dev_04_02 (2014-06-06)
OS: Linux - amd64 (3.2.5-gg1336)
JVM: 1.7.0-google-v6

projects: 8

open dart files: 6

auto-run pub: true
localhost resolves to: 127.0.0.1
mem max/total/free: 1778 / 823 / 233 MB
thread count: 63
index: 406232 relationships in 77582 keys in 222 sources

SDK installed: true
Dartium installed: true