summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py
diff options
context:
space:
mode:
authorJason Molenda <jmolenda@apple.com>2018-11-09 22:33:26 +0000
committerJason Molenda <jmolenda@apple.com>2018-11-09 22:33:26 +0000
commitc0e793d6543fc97c328dd3cf1b6f0708f3ec11be (patch)
treef5613921b2827a22276ef4bdcc5755b6adb7e7b7 /lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py
parent6c0bb3758e291ff34cd0cde885eae9b5f6f288f7 (diff)
downloadbcm5719-llvm-c0e793d6543fc97c328dd3cf1b6f0708f3ec11be.tar.gz
bcm5719-llvm-c0e793d6543fc97c328dd3cf1b6f0708f3ec11be.zip
Work with a gdb-remote target that doesn't handle the
qWatchpointSupportInfo packet correctly. In GDBRemoteCommunicationClient::GetWatchpointSupportInfo, if the response to qWatchpointSupportInfo does not include the 'num' field, then we did not get an answer we understood, mark this target as not supporting that packet. In Target.cpp, rename the very confusingly named CheckIfWatchpointsExhausted to CheckIfWatchpointsSupported, and check the error status returned by Process::GetWatchpointSupportInfo. If we cannot determine what the number of supported watchpoints are, assume that they will work. We'll handle the failure later when we try to create/enable the watchpoint if the Z2 packet isn't supported. Add a gdb_remote_client test case. <rdar://problem/42621432> llvm-svn: 346561
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/symbol-context/TestSymbolContext.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud