[vm] Improvements for --trace-debugger-stacktrace output. Improves the readability of the tracing output by adding beginning and ending markers for debugger stacktrace collection and using specific spacing instead of \t in output, so that output is more naturally nested via indention: * beginning/ending markers are not indented, * frames are indented by two spaces, and * additional output while collecting a frame is indented by four spaces. Adds tracing for DebuggerStackTrace::CollectAsyncAwaiters(). A different ending marker is used in the case when the collected trace is discarded due to a lack of async awaiters. ActivationFrame::GetSavedCurrentContext now takes an optional out parameter for the current context variable index, which is only used by CollectDartFrame and used to print the index there. This eliminates extra output when this method is used outside collecting stack traces. When the current context variable index is requested, GetSavedCurrentContext ignores the cached context if any so that the index is appropriately set if an appropriate variable is found. By default, skips tracing of non-collected frames and repeated async suspensions in async awaiter traces. Use the new --trace-debugger-stacktrace-verbose flag to add tracing for these cases. TEST=ci (tested manually, only affects debugging output) Change-Id: I2978d540f41b444251a61b62a57b6785a3dd8df0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/467300 Auto-Submit: Tess Strickland <sstrickl@google.com> Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Alexander Markov <alexmarkov@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.