TraceServer: Only reset upon stop while pid not UP

Before this fix, stopping upon an already exited server -while still
having the former pid stored- led to an extra stop act (with the
inaccurate warning messages shown as a result). Simply, only internally
reset in such a case, skipping the useless (and confusing) stopping act.

Contributes to fixing #8.

Signed-off-by: Marco Miller <marco.miller@ericsson.com>

Author: marco-miller

src/trace-server.ts

@@ -29,14 +29,14 @@ export class TraceServer {
         this.waitFor(context);
     }
 
-    stopOrReset(context: vscode.ExtensionContext | undefined) {
+    async stopOrReset(context: vscode.ExtensionContext | undefined) {
         const pid: number | undefined = context?.workspaceState.get(key);
         const not = prefix + ' not stopped as none running or owned by us.';
         if (pid === none) {
             vscode.window.showWarningMessage(not);
             return;
         }
-        if (pid) {
+        if (pid && (await this.isUp())) {
             let id: NodeJS.Timeout;
             // recovering from workspaceState => no this.server set
             if (this.server) {