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

[via lldb-commits]

Nerixyz wrote:

>(on Windows)?

That's the hard part 😅. I tried to get https://github.com/llvm/llvm-project/blob/main/lldb/test/API/tools/lldb-dap/threads/TestDAP_threads.py to run on Windows, but it's too flaky. From my observation, the debug adapter is too fast at launching the program before the test can set the breakpoints.
If I understand DAP correctly, then the server can send breakpoint requests after the connection has been initialized, but that doesn't seem to be easily doable in the tests right now[?] as `DAPTestCaseBase.launch` already does an initialization request (and launch request). Ideally, one could set the breakpoints inbetween.

I don't know why, but for some reason, my VS Code sends the launch request before existing breakpoints with lldb-dap, but when using the MSVC debugger from the cpptools (vsdbg), the breakpoints are sent before the launch request (as documented in [launch sequencing](https://microsoft.github.io/debug-adapter-protocol/overview#launch-sequencing)).

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