Pointer<T> instances were previously serialized as PlainInstance with no address, making them opaque to all debugger clients. TEST=pkg/vm_service/test/get_object_rpc_test.dart Fixes: https://github.com/dart-lang/sdk/issues/62853 Change-Id: Ia44eb0fa0851332409680d8d593141fe25505114 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/486460 Reviewed-by: Ben Konyi <bkonyi@google.com> Reviewed-by: Daco Harkes <dacoharkes@google.com> Auto-Submit: Nourhan Hasan <nourhan.m.hasan@gmail.com> Commit-Queue: Ben Konyi <bkonyi@google.com>
Observatory Developer Tooling
WARNING: This tooling is deprecated and maintained on a best-effort basis by members of the Dart VM team.
Activating Observatory
To easily serve Observatory without having to manually run webdev serve in this project, Observatory can be activated as a
global pub package and run via the observatory tool.
To do this, run dart bin/activate.dart, which will create the observatory script at $PUB_CACHE/bin.
Note: If any changes are made to bin/observatory.dart, dart bin/activate.dart must be re-run to pick up the changes.
Serving Observatory
To serve Observatory, simply run the observatory command. To automatically launch Observatory in Chrome, provide the --launch
flag.
Developing Observatory
When making changes to Observatory, run observatory --debug to run Observatory with DDC. This will allow for a more typical
web development workflow as changes to the Observatory sources will be picked up automatically on a page refresh.
Code Reviews
The development workflow of Dart (and Observatory) is based on code reviews.
Follow the code review instructions to be able to successfully submit your code.
The main reviewers for Observatory related CLs are:
- aam
- rmacnak