[Lldb-commits] [lldb] [lldb-dap] Treat empty thread names as unset (PR #141529)

[via lldb-commits]

Nerixyz wrote:

> The launch sequence is in parallel. Is it possible that the two debug adapter implements are handling them in different orders? It took me a while to realize this. I found this diagram enlightening: [microsoft/vscode#4902 (comment)](https://github.com/microsoft/vscode/issues/4902#issuecomment-368583522)

Ah, thank you! This cleared things up for me. I was a bit confused why I saw a third thread when debugging, but it turns out that the launch sequence is fine and it's Windows creating a thread pool in the background when calling WaitForSingleObject ([according to this SO answer](https://stackoverflow.com/a/63098682/16300717)), which is called in `thread.join()`.

I converted the tests to C++ now, as C's `<threads.h>` isn't supported everywhere. Furthermore, I only ignore the order of threads on Windows.

https://github.com/llvm/llvm-project/pull/141529