2 Commits

Author	SHA1	Message	Date
asiva@google.com	48418a75f7	Fix stack frame index numbers for full stack traces ... It used to be: #0 getCurrentStackTrace (file:///tmp/junk.dart:3:5) #0 func1 (file:///tmp/junk.dart:10:29) #1 func2 (file:///tmp/junk.dart:14:8) #2 func3 (file:///tmp/junk.dart:18:8) #3 func4 (file:///tmp/junk.dart:22:8) #4 main (file:///tmp/junk.dart:26:8) (Notice the two #0 frames on top). Now it will print this as: #0 getCurrentStackTrace (file:///tmp/junk.dart:3:5) #1 func1 (file:///tmp/junk.dart:10:29) #2 func2 (file:///tmp/junk.dart:14:8) #3 func3 (file:///tmp/junk.dart:18:8) #4 func4 (file:///tmp/junk.dart:22:8) #5 main (file:///tmp/junk.dart:26:8) Review URL: https://codereview.chromium.org//12381030 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@19272 260f80e4-7a28-3924-810f-c04153c831b5	2013-03-01 03:00:52 +00:00
asiva@google.com	3c90369ba6	Add functionality to get full stack trace when exceptions are thrown. ... This should address the issue raised in 7813. try { ... ... } on Object catch(e, s) { print(s.fullStackTrace); // This should print the full stack trace. } Review URL: https://codereview.chromium.org//12316116 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@19179 260f80e4-7a28-3924-810f-c04153c831b5	2013-02-27 22:47:06 +00:00