[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.

Start by comparing the attached first.txt and second.txt debug logs, then review the behavior described for the fake OpenOCD thread and the related #978 issue. Reproduce the first and second launch behavior with a multithreaded ARM application and verify that one debugger start remains connected when the initial thread is replaced.