We found a bug introduced by changes for the ScriptedProcess. It only manifests itself is you run a process with stop-at-entry set to true and when you are using an async debugger and when you are using a remote process. The solution is trivial. The majority of the patch is a test for stop-at-entry in the four cases of "sync & async" debugger crossed with "remote or local" process. The test both tests that stop-at-entry really does stop at entry, and then tests that we can resume afterwards.
I wrote the test for darwin because I don't know how to assert that we successfully stopped at entry on Linux or Windows. If someone more familiar with those platforms wants to extend the test to either of those hosts, it should be straightforward.
This hard coded port worries me for buildbot flakiness. Do other tests do this?