diff options
author | Dawn Perchik <dawn@burble.org> | 2015-10-01 21:15:43 +0000 |
---|---|---|
committer | Dawn Perchik <dawn@burble.org> | 2015-10-01 21:15:43 +0000 |
commit | 85872120853461be11327e37c74ba31fa5750372 (patch) | |
tree | 9171a3ec731acbeeecdf67c7ecacc227519d78cd /lldb/tools/lldb-mi/MICmdCmdSupportList.cpp | |
parent | 52bf0ebfdf48fa7e07257336e53a586088ee4df1 (diff) | |
download | bcm5719-llvm-85872120853461be11327e37c74ba31fa5750372.tar.gz bcm5719-llvm-85872120853461be11327e37c74ba31fa5750372.zip |
[lldb-mi] Add support for StopAtEntry in MI via "-exec-run --start".
This patch adds a --start option to the lldb-mi -exec-run command for
getting process stopped at entry point after launch. It is equivelent
to the -s option in the lldb command line interpreter:
process launch -s
and is therefore not supported on all hosts and/or targets. To check
if the --start option is supported, see if the corresponding feature
"exec-run-start-option" is in the list of options reported by the lldb-mi
"-list-features" command.
Patch from engineer.developer@gmail.com (Kirill Lapshin)
Reviewed by: ki.stfu
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12977
llvm-svn: 249072
Diffstat (limited to 'lldb/tools/lldb-mi/MICmdCmdSupportList.cpp')
-rw-r--r-- | lldb/tools/lldb-mi/MICmdCmdSupportList.cpp | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/lldb/tools/lldb-mi/MICmdCmdSupportList.cpp b/lldb/tools/lldb-mi/MICmdCmdSupportList.cpp index b36d2fd5e42..06d63612de6 100644 --- a/lldb/tools/lldb-mi/MICmdCmdSupportList.cpp +++ b/lldb/tools/lldb-mi/MICmdCmdSupportList.cpp @@ -71,8 +71,13 @@ CMICmdCmdSupportListFeatures::Execute() bool CMICmdCmdSupportListFeatures::Acknowledge() { - const CMICmnMIValueConst miValueConst("data-read-memory-bytes"); - const CMICmnMIValueList miValueList(miValueConst); + // Declare supported features here + const CMICmnMIValueConst miValueConst1("data-read-memory-bytes"); + const CMICmnMIValueConst miValueConst2("exec-run-start-option"); + // Some features may depend on host and/or target, decide what to add below + CMICmnMIValueList miValueList(true); + miValueList.Add(miValueConst1); + miValueList.Add(miValueConst2); const CMICmnMIValueResult miValueResult("features", miValueList); const CMICmnMIResultRecord miRecordResult(m_cmdData.strMiCmdToken, CMICmnMIResultRecord::eResultClass_Done, miValueResult); m_miResultRecord = miRecordResult; |