summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2016-03-16 09:44:49 +0000
committerPavel Labath <labath@google.com>2016-03-16 09:44:49 +0000
commit78fc4839808b432ac174b36204038bff63a986ef (patch)
tree3e53222e4122c52fcedab2476c265428870b643c /lldb/packages/Python/lldbsuite/test/lang/cpp
parent39aab4d60664a3ee56e7add57aafed453cab1df7 (diff)
downloadbcm5719-llvm-78fc4839808b432ac174b36204038bff63a986ef.tar.gz
bcm5719-llvm-78fc4839808b432ac174b36204038bff63a986ef.zip
[test] Persist packets between expect_gdbremote_sequence invocations
Summary: Some tests (Hc_then_Csignal_signals_correct_thread, at least) were sending a "continue" packet in one expect_gdbremote_sequence invocation, and "expecting" the stop-reply in another call. This posed a problem, because the were packets were not persisted between the two invocations, and if the stub was exceptionally fast to respond, the packet would be received in the first invocation (where it would be ignored) and then the second invocation would fail because it could not find the packet. Since doing matching in two invocations seems like a reasonable use of the packet pump, instead of fixing the test, I make sure the packet_pump supports this usage by making the list of captured packets persistent. Reviewers: tfiala Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D18140 llvm-svn: 263629
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud