summaryrefslogtreecommitdiffstats
path: root/llvm
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-09-09 22:05:48 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-09-09 22:05:48 +0000
commit9b961cc6043a3b84195ae7d938d2816c96f76303 (patch)
tree58529872536625c54578e57bc28db794e742e3a4 /llvm
parent2439b8b0c5f384561e005a64efe5c36b1007c6ff (diff)
downloadbcm5719-llvm-9b961cc6043a3b84195ae7d938d2816c96f76303.tar.gz
bcm5719-llvm-9b961cc6043a3b84195ae7d938d2816c96f76303.zip
[Reproducer] Disconnect when the replay server is out of packets.
This is a fix for the issue described in r371144. > On more than one occasion I've found this test got stuck during replay > while waiting for a packet from debugserver when the debugger was in > the process of being destroyed. When the replay server is out of packets we should just disconnect so the debugger doesn't have to do any cleanup that it wouldn't do during capture. llvm-svn: 371459
Diffstat (limited to 'llvm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud