Repository navigation
add a flag to flutter start to configure the observatory #43
Copy link
Copy link
Closed
Labels
c: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilitytoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
Activity
- addedtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
on Nov 7, 2015 cc @devoncarew still needed?
Yeah, this will let us setup breakpoints before the app starts running. It'll be important for a good UX.
- addedc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capability
on Dec 12, 2015 This is covered in more specifics by other issues, and is largely (completely?) implemented.
- added 7 commits that reference this issue
on Jul 26, 2018 24 remaining items
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 17, 2021
Metadata
Metadata
Assignees
Labels
c: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilitytoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
From https://github.com/flutter/tools/issues/111
Two things we'd want to do:
have it start the VM with the --pause_isolates_on_start=true flag
start it up listening on a specific port
The pause isolates flag will let us set breakpoints on isolates before they start running. Otherwise we'll miss breakpoints early in the app's lifecycle.