Closed maziac closed 2 years ago
Some more investigations: It seems that without changing the launch.json the debug adapter gets a disconnectRequest and then a launchRequest (note: supportsRestartRequest is false). In case the launch.json is changed it does not get the disconnectRequest.
With 3.0 this was fixed. But also the behavior is different now: If a restart is done and the launch.json was changed that the user is asked if he would like to terminate the current session. If yes, the session is terminated and the sequence ends here. I.e. the user has to press 'start' once again. Note: this only happens if the launch.json was changed. If it is untouched a restart really restarts the debug session.
DeZog 2.7.0 (also on develop branch).
Result:![Bildschirmfoto 2022-05-23 um 13 15 15](https://user-images.githubusercontent.com/3081973/169807442-d82083cb-6abb-486c-82ac-79320c3198c7.jpg)
This does not happen on normal restart. The launch.json need to be changed. This causes 'resolveDebugConfiguration' to be called. Probably this has to do with the problem.
Could be a vscode problem, see here: https://github.com/microsoft/vscode/issues/136200
Workaround: On next start of the debugger everything is working fine.