Note that we do know when we've actively suspended threads, but in an average
step, you will spend a fair bit of the time allowing all threads to run. So
that wouldn't allow a very accurate accounting.
Jim
> On Jun 3, 2016, at 8:42 AM, Jim Ingham via lldb-dev
> wrote:
>
>
>> On Jun 3, 201
> On Jun 3, 2016, at 2:22 AM, Abhishek Aggarwal via lldb-dev
> wrote:
>
> Hi everyone
>
> While debugging an inferior with LLDB, for every stop event a new StopID is
> generated and this ID can be extracted from SBProcess::GetStopID() API. This
> ID indicates change in the state of the proce
Hi everyone
While debugging an inferior with LLDB, for every stop event a new StopID is
generated and this ID can be extracted from SBProcess::GetStopID() API.
This ID indicates change in the state of the process between two stop
events.
As per my knowledge, in case of a multithreaded process thi
