update debug images

release-notes/v1_8.md

@@ -262,7 +262,7 @@ A first glimpse of _multi-target debugging_ was already available in the previou
 
 Using multi-target debugging is very simple: after you've started a first debug session, VS Code no longer blocks you from launching another session. As soon as a second session is up and running, the VS Code UI switches to _multi-target mode_:
 
-- The individual sessions now show up as top level elements in the CALL STACK view.
+- The individual sessions now show up as top level elements in the CALL STACK view.<BR>![Callstack View](images/1_8/debug-callstack.png)
 - The floating debug widget shows the currently _active session_ (and all other sessions are available in a dropdown menu).<BR>![Debug Actions Widget](images/1_8/debug-actions-widget.png)
 - Debug actions (e.g. all actions in the floating debug widget) are performed on the active session. The active session can be changed either by using the drop down menu in the floating debug widget or by selecting a different element in the CALL STACK view.
 - Whenever a session stops (e.g. because a breakpoint or exception is hit), this session becomes the active session. This makes it possible to easily step between debug sessions just by pressing 'F5'.
@@ -277,13 +277,15 @@ An alternative way to start multiple debug session is by using a so-called _comp
             "type": "node",
             "request": "launch",
             "name": "Server",
-            "program": "${workspaceRoot}/server.js"
+            "program": "${workspaceRoot}/server.js",
+            "cwd": "${workspaceRoot}"
         },
         {
             "type": "node",
             "request": "launch",
             "name": "Client",
-            "program": "${workspaceRoot}/client.js"
+            "program": "${workspaceRoot}/client.js",
+            "cwd": "${workspaceRoot}"
         }
     ],
     "compounds": [