SuibianP wrote: As it turns out that Win32 `execvp` actually [creates a new process instead of replace the current process image](https://github.com/python/cpython/issues/101191#issuecomment-1399013437), I changed the implementation to use `CreateProcess` before reporting the PID of the target.
The current implementation works with dape under emacs and should be functional, so I marked it ready for review. On VSCode however, while the extension is able to attach to the process and obtain sort of a stack backtrace, all breakpoints show up as unverified and does not trigger even if re-toggled. I am looking into it now. --- This is not relevant anymore but for the sake of completion: In the old implementation (wait for attach then `execvp`), the launcher process does get resumed after some 3 minutes. I still do not understand how it happened. https://github.com/llvm/llvm-project/pull/121269 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
