[vm] Refactor vm/dart/use_dwarf_stack_traces_flag tests. Both the regular and deferred versions of this test contain up to six different test cases: All platforms: * ELF snapshot, using DWARF from the snapshot * ELF snapshot, using DWARF from the separate debugging information For platforms where the test can assemble snapshots: * assembled snapshot, using DWARF from the snapshot or the separate .dSYM package on MacOS * assembled snapshot, using DWARF from the separate debugging information For MacOS only: * creating a single-architecture universal binary from the separate .dSYM package and extracting DWARF information from it * creating a multi-architecture universal binary from the separate .dSYM package and extracting DWARF information from it Originally the tests were written using package:expect, performing program compilation and execution separately before each test and lazily reading DWARF information within the test itself. Since tests using package:expect stop the program immediately on a failure, a failing expectation keeps other independent test cases from being checked. However, it's useful to know if the failure is limited to only a subset of the test cases, since that helps point at which code is to blame for the test failure(s). Now the tests are refactored to first set up the tests by performing all program compilation and execution first, collecting all outputs and DWARF information as test state. Then the test cases are defined over the collected test state using package:test instead of package:expect. This way, as long as there is not a failure in the initial setup, all of the applicable test cases are run even if one or more of them fail. ----- In pkg/native_stack_traces, changes the return types of the reader retrieval methods in the DwarfContainer class and DwarfSnapshot.fromDwarfContainer to be nullable. If the shared object does not contain the expected DWARF information, these methods now return null instead of causing null check exceptions to be thrown. Issue: https://github.com/dart-lang/sdk/issues/55612 Change-Id: I253965a95894f455e51d021e32dbf2703d8b99cf Cq-Include-Trybots: luci.dart.try:vm-aot-dwarf-linux-product-x64-try,vm-aot-linux-debug-x64-try,vm-aot-mac-release-arm64-try,vm-aot-mac-product-arm64-try,vm-aot-mac-release-x64-try,vm-aot-win-debug-arm64-try,vm-aot-win-debug-x64-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/375240 Commit-Queue: Tess Strickland <sstrickl@google.com> Reviewed-by: Daco Harkes <dacoharkes@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.