aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/SafeStack.cpp
diff options
context:
space:
mode:
authorjimingham <jingham@apple.com>2023-11-30 09:48:04 -0800
committerGitHub <noreply@github.com>2023-11-30 09:48:04 -0800
commitd1bf1947e4e4f3ef75f2ba3ac9aa77dc38214de1 (patch)
treed443633500da7e90d4fb137e76aca8312a1a8ad4 /llvm/lib/CodeGen/SafeStack.cpp
parentcb13e9286b6d4e384b5d4203e853d44e2eff0f0f (diff)
downloadllvm-d1bf1947e4e4f3ef75f2ba3ac9aa77dc38214de1.zip
llvm-d1bf1947e4e4f3ef75f2ba3ac9aa77dc38214de1.tar.gz
llvm-d1bf1947e4e4f3ef75f2ba3ac9aa77dc38214de1.tar.bz2
Send an explicit interrupt to cancel an attach waitfor. (#72565)
Currently when you interrupt a: (lldb) process attach -w -n some_process lldb just closes the connection to the stub and kills the lldb_private::Process it made for the attach. The stub at the other end notices the connection go down and exits because of that. But when communication to a device is handled through some kind of proxy server which isn't as well behaved as one would wish, that signal might not be reliable, causing debugserver to persist on the machine, waiting to steal the next instance of that process. We can work around those failures by sending an explicit interrupt before closing down the connection. The stub will also have to be waiting for the interrupt for this to make any difference. I changed debugserver to do that. I didn't make the equivalent change in lldb-server. So long as you aren't faced with a flakey connection, this should not be necessary.
Diffstat (limited to 'llvm/lib/CodeGen/SafeStack.cpp')
0 files changed, 0 insertions, 0 deletions