Hi everyone,
We have started a meetup page for LLVM socials in Sweden [1]. Thanks
to those that have already joined!
We're going to keep most of the communication there from now on.
Hopefully towards the end of next week I'll post another Doodle for
scheduling the next event, which will take plac
On 16 March 2017 at 21:43, Kamil Rytarowski wrote:
> On 16.03.2017 11:55, Pavel Labath wrote:
>> What kind of per-process events
>> are we talking about here?
>
> I'm mostly thinking about ResumeActions - to resume the whole process,
> while being able single-stepping desired thread(s).
>
> (We al
On 17.03.2017 01:37, Jim Ingham wrote:
> The main consumer of thread stop reasons is the execution control
> (ThreadPlans - which handle stepping & function calling - and
> StopInfo::PerformAction which handles breakpoint/watchpoint hits). The only
> bad effect of populating all the threads wit
On 17.03.2017 10:48, Pavel Labath wrote:
> On 16 March 2017 at 21:43, Kamil Rytarowski >
>> I imagined a possible flow of ResumeAction calls like:
>> [Generic/Native framework knows upfront the image of threads within
>> debuggee]
>> - Resume Thread 2 (PT_RESUME)
>> - Suspend Thread 3 (PT_SUSPEND
From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Pavel
Labath via lldb-dev
Sent: Friday, March 17, 2017 4:48 AM
> On 16 March 2017 at 21:43, Kamil Rytarowski wrote:
>> I imagined a possible flow of ResumeAction calls like:
>> [Generic/Native framework knows upfront the imag
