labath wrote: I can see this too, and can reproduce it pretty much 100% of the time. The `GetRunLock` hypothesis seems believable because the process launching code (Process::LaunchPrivate) is mucking around with the private state thread.
It's also possible this doesn't reproduce on darwin because it goes through a different launching code path (basically it never launches, only attaches). I think we'll need to revert this for now, as it makes it more or less impossible to have a normal debug session (things actually work if you type "continue" after this error, but there's no indication that that is an option). https://github.com/llvm/llvm-project/pull/134757 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
