Funny behavior when the user tries to terminate the target before it stops for the first time

[xusheng6]

If the user sets debugger.stopAtEntryPoint to false, the target process will run on its own and not stop. Right now, we are not creating the debugger binary view (and do some other initialization tasks) until the target stops for the first time. As a result, in this case, these operations would not have been done if the user decides to kill the target. And what happens next is funny, that the debugger will try to create the debugger view after the target has been killed.

I noticed this behavior while working on https://github.com/Vector35/debugger/issues/547