forked from OSchip/llvm-project
8ccfcab34f
Previously we would persist the flags indicating whether the remote side supports a particular feature across reconnects, which is obviously not a good idea. I implement the clearing by nuking (its the only way to be sure :) the entire GDBRemoteCommunication object in the disconnect operation and creating a new one upon connection. This allows us to maintain a nice invariant that the GDBRemoteCommunication object (which is now a pointer) exists only if it is connected. The downside to that is that a lot of functions now needs to check the validity of the pointer instead of blindly accessing the object. The process communication does not suffer from the same issue because we always destroy the entire Process object for a relaunch. Differential Revision: https://reviews.llvm.org/D116539 |
||
|---|---|---|
| .. | ||
| builders | ||
| make | ||
| test_runner | ||
| tools | ||
| README-TestSuite | ||
| __init__.py | ||
| bench.py | ||
| concurrent_base.py | ||
| configuration.py | ||
| decorators.py | ||
| dotest.py | ||
| dotest_args.py | ||
| gdbclientutils.py | ||
| lldb_pylint_helper.py | ||
| lldbbench.py | ||
| lldbdwarf.py | ||
| lldbgdbclient.py | ||
| lldbinline.py | ||
| lldbpexpect.py | ||
| lldbplatform.py | ||
| lldbplatformutil.py | ||
| lldbtest.py | ||
| lldbtest_config.py | ||
| lldbutil.py | ||
| test_categories.py | ||
| test_result.py | ||