Fix a gdbremote bug in _M/_m stub support detection.
authorTodd Fiala <todd.fiala@gmail.com>
Sat, 21 Jun 2014 00:48:09 +0000 (00:48 +0000)
committerTodd Fiala <todd.fiala@gmail.com>
Sat, 21 Jun 2014 00:48:09 +0000 (00:48 +0000)
commitf105f588b31b4384bb48f528784cb05ae0eec060
tree9188c052211583fb8522a9ac3b1ef61f15e6a75a
parentd119fa028ac28ed4ec0bf11d1178bf58dedf72a7
Fix a gdbremote bug in _M/_m stub support detection.

When a stub reported $#00 (unsupported) for _M and _m
packets, the unsupported response was not handled and
the client then marked the _M/_m commands as definitely
supported.  However, they would always fail, preventing
lldb's fallback InferiorCallMmap-based allocation strategy
from being used to attempt to allocate memory in the inferior
process space.

llvm-svn: 211425
lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp