Oops... sent too soon :P
I meant to write this:
lldb::SBCommandReturnObject ret;
m_debugger.GetCommandInterpreter().HandleCommand("thread step-over", ret);
Where m_debugger is the instance of SBDebugger
Eran
On Thu, Sep 4, 2014 at 6:45 PM, Eran Ifrah <eran.if...@gmail.com> wrote:
> From my experience, any command that can be used by the API can be invoked
> problematically like this:
>
>
>
>
> On Thu, Sep 4, 2014 at 10:54 AM, Mario Zechner <badlogicga...@gmail.com>
> wrote:
>
>> Hi,
>>
>> i'm currently working on a debugger based on the public LLDB API and am
>> currently looking into multi-threaded debugging. The debugger should
>> support the following scenario:
>>
>> - user sets breakpoints
>> - two or more threads get stopped due to breakpoints
>> - user wants to continue execution of only one of the threads
>>
>> SBThread has the methods Suspend/Resume. To my understanding (and tests),
>> Suspend marks a thread as not to be continued when the entire process is
>> continued. Which is the oposite of what i'd need for my use case.
>>
>> I looked into the implementation of the command 'thread continue', but
>> that uses the private LLDB API, which is sadly not an option for us at this
>> point.
>>
>> I'd be greatful for any hints.
>>
>> Thanks,
>> Mario
>>
>> _______________________________________________
>> lldb-dev mailing list
>> lldb-dev@cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>
>>
>
>
> --
> Eran Ifrah,
> Author of codelite, a cross platform open source C/C++ IDE:
> http://www.codelite.org
> CodeLite IDE Blog: http://codeliteide.blogspot.com/
>
--
Eran Ifrah,
Author of codelite, a cross platform open source C/C++ IDE:
http://www.codelite.org
CodeLite IDE Blog: http://codeliteide.blogspot.com/
_______________________________________________
lldb-dev mailing list
lldb-dev@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
