[Lldb-commits] [PATCH] Python Split [2/2] - Content change
Zachary Turner
zturner at google.com
Thu Mar 5 15:26:14 PST 2015
Makes sense, I will work on this today. Thanks
On Thu, Mar 5, 2015 at 3:21 PM Greg Clayton <clayborg at gmail.com> wrote:
> SBDebugger::Initialize () is the main function that must be called prior
> to using anything in the lldb::SB* layer, and it currently looks like:
>
> void
> SBDebugger::Initialize ()
> {
> Log *log(GetLogIfAllCategoriesSet (LIBLLDB_LOG_API));
>
> if (log)
> log->Printf ("SBDebugger::Initialize ()");
>
> SBCommandInterpreter::InitializeSWIG ();
>
> Debugger::Initialize(LoadPlugin);
> }
>
> You might need to call Debugger::Initialize() first so all plug-ins
> registers themselves, and then call SBCommandInterpreter::InitializeScriptInterpreters()
> after to ensure everything is setup as the ScriptInterpreterPython will
> need to register itself with the ScriptInterpreter if it already isn't
> doing so.
>
>
> http://reviews.llvm.org/D7957
>
> EMAIL PREFERENCES
> http://reviews.llvm.org/settings/panel/emailpreferences/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150305/033291e8/attachment.html>
More information about the lldb-commits
mailing list