Re: [lldb-dev] Can I call a python script from LLDB c++ code?

Responses inline -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project > -Original Message- > From: Greg Clayton [mailto:clayb...@gmail.com] > Sent: Tuesday, April 03, 2018 5:19 PM > To: Ted Wood

Re: [lldb-dev] Can I call a python script from LLDB c++ code?

> On Apr 3, 2018, at 12:18 PM, Ted Woodward via lldb-dev > wrote: > > LLDB for Hexagon can automatically launch and connect to the Hexagon > simulator, much like LLDB can launch and connect to debugserver/lldb-server. > I've got a copy of GDBRemoteCommunication::StartDebugserverProcess that do

[lldb-dev] Can I call a python script from LLDB c++ code?

LLDB for Hexagon can automatically launch and connect to the Hexagon simulator, much like LLDB can launch and connect to debugserver/lldb-server. I've got a copy of GDBRemoteCommunication::StartDebugserverProcess that does this. A copy because there are feature incompatibilities between hexagon-sim

Re: [lldb-dev] GDB RSPs non-stop mode capability in v5.0

> On Apr 3, 2018, at 1:28 AM, Ramana wrote: > > > > On Thu, Mar 29, 2018 at 11:17 PM, Jim Ingham > wrote: > The breakpoints aren't a structural problem. If you can figure out a > non-code modifying way to handle breakpoints, that would be a very surgical > change

Re: [lldb-dev] GDB RSPs non-stop mode capability in v5.0

On Mon, 2 Apr 2018 at 16:28, Greg Clayton via lldb-dev < lldb-dev@lists.llvm.org> wrote: > > > On Apr 2, 2018, at 6:18 AM, Ramana wrote: > > > > On Thu, Mar 29, 2018 at 8:02 PM, Greg Clayton wrote: > >> >> >> On Mar 29, 2018, at 2:08 AM, Ramana via lldb-dev >> wrote: >> >> Hi, >> >> It appears

Re: [lldb-dev] GDB RSPs non-stop mode capability in v5.0

On Thu, Mar 29, 2018 at 11:17 PM, Jim Ingham wrote: > The breakpoints aren't a structural problem. If you can figure out a > non-code modifying way to handle breakpoints, that would be a very surgical > change. And as Fred points out, out of place execution in the target would > be really handy