New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing legacy debug protocol from VM #24209
Comments
@sethladd , should we move this bug to 1.14? This wont happen until then, right? |
@iposva-google moving to you now that we are in 1.14. |
Is WebStorm using the new protocol already or will WebStorm debugging break with bleeding_edge in a few days @alexander-doroshko? |
WebStorm already uses new VM Service protocol for debugging in case of SDK 1.14+ |
@alexander-doroshko Great! Thanks for the confirmation. |
dear @alexander-doroshko, When I tried to work on my Mac (El Captain) & WebStorm 10.0.4 , and I got the problem below.
|
@EasonPai New VM Service Protocol is used for debugging if 2 conditions are met:
To make sure that VM Service Protocol is used for debugging see Dart VM command line: there should be no --debug:XXXX flag. In your case it is there and it confirms that you need to update your IDE. |
Thanks for the info. |
@EasonPai WebStorm 10 was released on March 31, 2015. Dart SDK 1.14 was released 10 months later, on 29 of January, 2016. At that moment WebStorm 11 was already out and was already able to debug via new protocol. You shouldn't expect old IDE to support new technologies. |
The Dart VM Service Protocol is now spec'ed and battle tested.
The legacy debug protocol is now deprecated. We intend to remove this support in 1.13. We encourage tool vendors to use the new Service Protocol for debugging a Dart VM.
The text was updated successfully, but these errors were encountered: