summaryrefslogtreecommitdiff
path: root/lldb/test/API/python_api/process/cancel_attach
AgeCommit message (Collapse)Author
2024-11-11[lldb] Disable TestCancelAttach for Windows host (#115619)Dmitry Vasilyev
See #115618 for details.
2024-02-15[lldb] Fix Python test formatting (NFC)Jonas Devlieghere
2023-11-30Send an explicit interrupt to cancel an attach waitfor. (#72565)jimingham
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.