summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
diff options
context:
space:
mode:
authorGreg Clayton <gclayton@apple.com>2012-10-13 02:07:45 +0000
committerGreg Clayton <gclayton@apple.com>2012-10-13 02:07:45 +0000
commit998255bfe841a4191d458a56aae0267f673b1a72 (patch)
treeada5b24a203f1a24e041f9cce2188283d037de98 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
parent88db3171dd5dcc54e3890b6f823c60831fc520a5 (diff)
downloadbcm5719-llvm-998255bfe841a4191d458a56aae0267f673b1a72.tar.gz
bcm5719-llvm-998255bfe841a4191d458a56aae0267f673b1a72.zip
<rdar://problem/12491387>
I added the ability for a process plug-in to implement custom commands. All the lldb_private::Process plug-in has to do is override: virtual CommandObject * GetPluginCommandObject(); This object returned should be a multi-word command that vends LLDB commands. There is a sample implementation in ProcessGDBRemote that is hollowed out. It is intended to be used for sending a custom packet, though the body of the command execute function has yet to be implemented! llvm-svn: 165861
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud