[ARM] Need to run debugging session twice when debugging multithreaded application

Here is:
cpptools v0.13.0
VSCode 1.16.1
Windows 8

I use VS Code to develop application for the ARM Cortem-Mx MCUs. When starting debugger with multithreaded application (with OpenOCD threads support) I need to run debugger session twice - first time VS Code drops debugging session. Standalone gdb-OpenOCD session runs flawlessly.

That is not a big problem, cause debugger functions properly after the second start, but it looks like something is broken.

Here is the debug log of the VSCode for the first debugger start:
first.txt

And here is for the second one:
second.txt

Note: when application starts there is no OS running yet, so OpenOCD reports there is a fake thread (thread id 1). This thread terminates on OS start and new real threads created.

The problem may be related to #978 issue.

Beginne damit, die angehängten Debug-Logs first.txt und second.txt zu vergleichen, überprüfe anschließend das für den Fake-OpenOCD-Thread beschriebene Verhalten und das zugehörige Issue #978. Reproduziere das Verhalten beim ersten und zweiten Start mit einer multithreaded ARM-Anwendung und verifiziere, dass ein Debugger-Start verbunden bleibt, wenn der initiale Thread ersetzt wird.