summaryrefslogtreecommitdiffstats
path: root/lldb/source/Expression/ClangExpressionParser.cpp
diff options
context:
space:
mode:
authorGreg Clayton <gclayton@apple.com>2011-05-15 23:46:54 +0000
committerGreg Clayton <gclayton@apple.com>2011-05-15 23:46:54 +0000
commit17a0cb68c97eb551e50431470d68ab17b58e9ccc (patch)
tree8e49d0dd6a50ed1f4010258ed1fc0ada777bc2db /lldb/source/Expression/ClangExpressionParser.cpp
parent5d353156d0104f7ed325e26e0fe4f3981665801c (diff)
downloadbcm5719-llvm-17a0cb68c97eb551e50431470d68ab17b58e9ccc.tar.gz
bcm5719-llvm-17a0cb68c97eb551e50431470d68ab17b58e9ccc.zip
Properly handle when commands are not unsupported in the GDB remote clients.
Prior to this fix we would often call SendPacketAndWaitForResponse() which returns the number of bytes in the response. The UNSUPPORTED response in the GDB remote protocol is zero bytes and we were checking for it inside an if statement: if (SendPacketAndWaitForResponse(...)) { if (response.IsUnsupportedResponse()) { // UNSUPPORTED... // This will never happen... } } We now handle is properly as: if (SendPacketAndWaitForResponse(...)) { } else { // UNSUPPORTED... } llvm-svn: 131393
Diffstat (limited to 'lldb/source/Expression/ClangExpressionParser.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud