On 17 March 2017 at 16:23, Ted Woodward wrote:
>
>
> 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 ca
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
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
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 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
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 with the whole process signals is if any of the pl
On 16.03.2017 22:59, Jim Ingham wrote:
> But it looks like all the "whole process" events you are talking about are
> not stop reasons but more start actions. That makes sense, but what whole
> process stop events do you mean?
A process can be stopped with a signal. A signal can be emitted to:
> On Mar 16, 2017, at 2:43 PM, Kamil Rytarowski via lldb-dev
> wrote:
>
> On 16.03.2017 11:55, Pavel Labath wrote:
>> On 16 March 2017 at 00:43, Kamil Rytarowski wrote:
>>>
>>> TODO:
>>> - Fixing software breakpoints support,
>
> Fixed!
>
> 267->596 of succeeded tests out of 1200+ - please
On 16.03.2017 11:55, Pavel Labath wrote:
> On 16 March 2017 at 00:43, Kamil Rytarowski wrote:
>>
>> TODO:
>> - Fixing software breakpoints support,
Fixed!
267->596 of succeeded tests out of 1200+ - please scroll for details.
>> - Special Registers (Floating Point..) reading/writing,
>> - Unl
On 16 March 2017 at 00:43, Kamil Rytarowski wrote:
> On 01.03.2017 10:13, Kamil Rytarowski wrote:
>> Hello,
>>
>> The contract for the LLDB port on NetBSD has been prolonged by The
>> NetBSD Foundation. The additional time will cover the features that were
>> delayed in order to address blockers t
On 01.03.2017 10:13, Kamil Rytarowski wrote:
> Hello,
>
> The contract for the LLDB port on NetBSD has been prolonged by The
> NetBSD Foundation. The additional time will cover the features that were
> delayed in order to address blockers that were unveiled during the work
> that has been done.
>
11 matches
Mail list logo
