3ca4243818
Sometimes we see unhandled exceptions during this setup work, see: - https://github.com/flutter/flutter/issues/148346 - https://github.com/flutter/flutter/issues/148348 Currently these are unhandled and bring the debug adapter down. In VS Code, the error (send to stderr) is not visible to the user so they just see a silent crash which makes it very difficult to report (and the Flutter crash reports don't have any context). This change will send the exception to the client and then cleanly terminate, which should give the user more information to open a good bug report (assuming the issue wasn't just something like them terminating the app as it was starting). Change-Id: I4aefbc278e6a0708924c6fa41c5179d581117689 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/366662 Reviewed-by: Ben Konyi <bkonyi@google.com> Reviewed-by: Helin Shiah <helinx@google.com> Commit-Queue: Ben Konyi <bkonyi@google.com>