aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2025-11-06 14:17:51 -0800
committerGitHub <noreply@github.com>2025-11-06 14:17:51 -0800
commitfa83723bbe55f2aee857438f8087c4fc0f52449e (patch)
tree5657dc9019dc4de51e8b5f0a22410e0065e0a26a /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent4b4bfe9ceb48b69bafa38bc13ca34c1daea1fc06 (diff)
downloadllvm-fa83723bbe55f2aee857438f8087c4fc0f52449e.zip
llvm-fa83723bbe55f2aee857438f8087c4fc0f52449e.tar.gz
llvm-fa83723bbe55f2aee857438f8087c4fc0f52449e.tar.bz2
[debugserver] Remove unnecessary sleep in MachProcess::AttachForDebug (#166674)
Remove the unnecessary sleep in MachProcess::AttachForDebug. The preceding comment makes it seem like it's necessary for synchronization, though I don't believe that's the case (see below), and even if it were, sleeping is not a reliable way to achieve that. The reason I don't believe it's necessary is because after we return, we synchronize with the exception thread on a state change. The latter will call and update the process state, which is exactly what we synchronize on. I was able to verify that this is the first time we change the process state: i.e., `GetState` doesn't return a different value before and after the sleep. On top of that, there are 3 more places where we call ptrace attach (`PosixSpawnChildForPTraceDebugging`, `SBLaunchForDebug`, and `BoardServiceLaunchForDebug`) where we don't sleep. rdar://163952037
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions