Chromium Code Reviews| Index: runtime/bin/vmservice/vmservice_io.dart |
| diff --git a/runtime/bin/vmservice/vmservice_io.dart b/runtime/bin/vmservice/vmservice_io.dart |
| index 409bc5972a0c110d842c0da006e319a958bef8ff..631cf8d5e277aa36fc5fa5ada52123a162b1e9f4 100644 |
| --- a/runtime/bin/vmservice/vmservice_io.dart |
| +++ b/runtime/bin/vmservice/vmservice_io.dart |
| @@ -89,6 +89,14 @@ main() { |
| // scheduled microtasks. |
| Timer.run(() {}); |
| } |
| + // TODO(johnmccutchan, turnidge) Creating a VMService object here causes |
| + // strange behavior from the legacy debug protocal and coverage tool. |
| + // Enable this code, and remove the call to Isoate::KillIsolate() from |
|
turnidge
2015/08/04 21:39:02
protocal -> protocol, Isoate -> Isolate.
zra
2015/08/05 06:23:06
Done and added link to issue.
|
| + // service_isolate.cc when the strange behavior is solved. |
| + // else { |
| + // var service = new VMService(); |
| + // service.onShutdown = _onShutdown; |
| + // } |
| scriptLoadPort.handler = _processLoadRequest; |
| // Register signal handler after a small delay to avoid stalling main |
| // isolate startup. |