[dart-misc] Intent to Remove: VM's legacy debug protocol

['Seth Ladd' via Dart Misc]

(BCC ***@dartlang.org)

We intend to remove the VM's legacy debug protocol in the first 1.14-dev
channel build. The 1.13 SDK will be the last SDK to ship with the legacy
protocol in the VM.

Developers writing debuggers should move to the VM's Service Protocol,
described here
<https://github.com/dart-lang/sdk/blob/master/runtime/vm/service/service.md>.
Wrapper libraries are here <https://github.com/dart-lang/vm_service_drivers>
.

Most users are probably not directly using the VM's legacy debug protocol,
and thus we expect minimal impact on end users. We have been working with
tool vendors [*] to implement the new Service Protocol in time for Dart
SDK's 1.14 release.

If you feel this removal impacts your work, please file an issue:
http://dartbug.com


[*] the eclipse plugin for Dart will not be migrated to the new service
protocol, and thus stand-alone debugging in the eclipse plugin will stop
working with Dart 1.14. If you are using the Eclipse plugin, and you want
to debug the stand-alone VM, we recommend that you use IntelliJ or WebStorm
or Observatory.

[Kasper Peulen]

Is there anything that will noticibly change in Webstorm/IntelliJ debugging
once this is integrated and the old one removed?

Post by 'Seth Ladd' via Dart Misc
We intend to remove the VM's legacy debug protocol in the first 1.14-dev
channel build. The 1.13 SDK will be the last SDK to ship with the legacy
protocol in the VM.
Developers writing debuggers should move to the VM's Service Protocol,
described here
<https://github.com/dart-lang/sdk/blob/master/runtime/vm/service/service.md>.
Wrapper libraries are here
<https://github.com/dart-lang/vm_service_drivers>.
Most users are probably not directly using the VM's legacy debug protocol,
and thus we expect minimal impact on end users. We have been working with
tool vendors [*] to implement the new Service Protocol in time for Dart
SDK's 1.14 release.
http://dartbug.com
[*] the eclipse plugin for Dart will not be migrated to the new service
protocol, and thus stand-alone debugging in the eclipse plugin will stop
working with Dart 1.14. If you are using the Eclipse plugin, and you want
to debug the stand-alone VM, we recommend that you use IntelliJ or WebStorm
or Observatory.
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

--
Kasper

[Jan Mostert]

What will the new debug process be for web based applications?
pub serve --mode="debug"
And then remotely attach a debugger?

Post by Kasper Peulen
Is there anything that will noticibly change in Webstorm/IntelliJ
debugging once this is integrated and the old one removed?
On Tue, Oct 6, 2015 at 6:37 PM, 'Seth Ladd' via Dart Misc <

Post by 'Seth Ladd' via Dart Misc
We intend to remove the VM's legacy debug protocol in the first 1.14-dev
channel build. The 1.13 SDK will be the last SDK to ship with the legacy
protocol in the VM.
Developers writing debuggers should move to the VM's Service Protocol,
described here
<https://github.com/dart-lang/sdk/blob/master/runtime/vm/service/service.md>.
Wrapper libraries are here
<https://github.com/dart-lang/vm_service_drivers>.
Most users are probably not directly using the VM's legacy debug
protocol, and thus we expect minimal impact on end users. We have been
working with tool vendors [*] to implement the new Service Protocol in time
for Dart SDK's 1.14 release.
http://dartbug.com
[*] the eclipse plugin for Dart will not be migrated to the new service
protocol, and thus stand-alone debugging in the eclipse plugin will stop
working with Dart 1.14. If you are using the Eclipse plugin, and you want
to debug the stand-alone VM, we recommend that you use IntelliJ or WebStorm
or Observatory.
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

--
Kasper
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
To unsubscribe from this group and stop receiving emails from it, send an

[Alexander Doroshko]

Post by Kasper Peulen
Is there anything that will noticibly change in Webstorm/IntelliJ
debugging once this is integrated and the old one removed?

No, debugging experience will remain pretty much the same.

[George Moschovitis]

Post by 'Seth Ladd' via Dart Misc
[*] the eclipse plugin for Dart will not be migrated to the new service
protocol, and thus stand-alone debugging in the eclipse plugin will stop
working with Dart 1.14. If you are using the Eclipse plugin, and you want
to debug the stand-alone VM, we recommend that you use IntelliJ or WebStorm
or Observatory.

Is it really soo difficult to update the eclipse plugin with support for
the new protocol? Eclipse + the plugin is a great env for dart coding and I
would love to be able to continue using it.