[Lldb-commits] [PATCH] D12977: LLDB MI addition for getting process stopped at first instruction right after launch via -exec-run
Vadim Macagon via lldb-commits
lldb-commits at lists.llvm.org
Sat Sep 19 22:48:16 PDT 2015
enlight added a subscriber: enlight.
enlight added a comment.
According to the GDB-MI spec the exec-run <https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Program-Execution.html#GDB_002fMI-Program-Execution> command already has a **start** option. Support for the **start** option can be detected by checking for **exec-run-start-option** in the list of features returned by the list-features <https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Support-Commands.html#GDB_002fMI-Support-Commands> command. So, what's the rationale for diverging from the spec in this case?
In GDB your example would be written as:
Comment at: tools/lldb-mi/MICmdCmdExec.cpp:92
@@ +91,3 @@
+ const char *pCmd = bProcessMustStopAtEntry ? "process launch -s" : "process launch";
+ const lldb::ReturnStatus rtn = rSessionInfo.GetDebugger().GetCommandInterpreter().HandleCommand(pCmd, m_lldbResult);
The process should be launched through the SB API, not the command interpreter. I'm not very familiar with the SB API but I'd try using the **lldb::eLaunchFlagStopAtEntry** flag with **SBLaunchInfo::SetLaunchFlags()**.
More information about the lldb-commits