[lldb-dev] Remote Non-Stop Mode
Ted Woodward
ted.woodward at codeaurora.org
Tue May 19 12:28:44 PDT 2015
We also need to think about behavior when switching states.
For example, if we're in all-stop mode with all threads stopped, then switch
to non-stop mode and do a continue, which threads to we run? All of them?
One of them (which one?)?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
-----Original Message-----
From: lldb-dev-bounces at cs.uiuc.edu [mailto:lldb-dev-bounces at cs.uiuc.edu] On
Behalf Of Jim Ingham
Sent: Tuesday, May 19, 2015 1:20 PM
To: Ewan Crawford
Cc: lldb-dev at cs.uiuc.edu
Subject: Re: [lldb-dev] Remote Non-Stop Mode
> On May 19, 2015, at 7:13 AM, Ewan Crawford <ewan at codeplay.com> wrote:
>
> Switching to non-stop during a session I don't think would be too hard
once we've got it working. As all the packoet handling will be there, and
we'd just need t add a way to send a QNonStop packet when switching.
> It might however uncover some bugs in the stepping logic which could be
tricky to track down.
Doing this is a great project, but getting this to work reliably will be
quite a bit of work. I bet there will be lots of bugs that will not be at
all tricky to track down, just tricky to fix...
Jim
>
_______________________________________________
lldb-dev mailing list
lldb-dev at cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
More information about the lldb-dev
mailing list