Dodzey wrote: @clayborg Yes, it appears to. For context my workflow is C++ development, using recent versions of Clang and GCC. In VS Code I use the Microsoft CPPTools extension to allow for GDB debugging of GCC builds, with intellisense disabled. I am using clangd for auto-completion, inlay hints, automatic compiler errors/warning squiggles etc. That combination means that I have the Microsoft CPPTools extension enabled, which is enough for the 'workaround' here to be functional. I've tested launching the debugger twice within VSCode and using the process selection dropdown picker attaching to two copies of the same executable running at the same time. Both debuggers seem to be working ok and operating concurrently as you would expect.
https://github.com/llvm/llvm-project/pull/75342 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
