The eStateSuspended state is used for threads (you can set it via
SBThread::Suspend/Resume). It controls whether a "continue" operation
on the process will run the thread or not.
I am not sure if you can ever see that state on the process itself.
On Sat, 14 Jul 2018 at 15:39, Adrian Prantl via lldb-dev
<lldb-dev@lists.llvm.org> wrote:
>
>
>
> > On Jul 13, 2018, at 10:59 PM, Александр Поляков <polyakov....@gmail.com>
> > wrote:
> >
> > Hi lldb-dev,
> >
> > I'm looking at re-implementing of
> > CMICmnLLDBDebugHandleEvents::HandleProcessEventStateSuspended to get rid of
> > HandleCommand("process status") hack and use SB API instead. To check my
> > changes I need to get HandleProcessEventStateSuspended called, so could
> > someone help me with a sequence of lldb-mi commands which will call
> > HandleProcessEventStateSuspended.
>
> Other than reading through the code and manually tracing a sequence where
> this function gets called, one simple trick you can try is to put an
> assert(false) into HandleProcessEventStateSuspended, run the testsuite (or
> perform an lldb-mi debug session) and look for a testacase that triggers the
> new assertion.
>
> -- adrian
>
> >
> > Thanks in advance.
> >
> > --
> > Alexander
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
