Re: [lldb-dev] Stepping in a breakpoint callback with Python

2019-09-27 Thread Jim Ingham via lldb-dev
So the problem you are having is getting the scripted step started in "trace" with the SBThread::StepUsingScriptedStep? Did you try passing False for "resume_immediately" and then returning False from "trace". The explanation for: # XXX: Doesn't seem to matter with 'thread step-scripted

Re: [lldb-dev] Stepping in a breakpoint callback with Python

2019-09-27 Thread Nikita Karetnikov via lldb-dev
Jim, > Does that simple use of the scripted plan also work for you? No, that doesn't work for me. My original script does more stuff, so I need to pass the state via global variables. However, I think I've figured out a way to do what I want: https://gist.github.com/nkaretnikov/75c8a0b814246b32

Re: [lldb-dev] lldb warning or developer options

2019-09-27 Thread Sourabh Singh Tomar via lldb-dev
Hi Pavel, Thanks for sharing this, I'll look into this. -- Sourabh Singh Tomar On Fri, Sep 27, 2019 at 12:18 PM Pavel Labath wrote: > On 27/09/2019 07:52, Sourabh Singh Tomar via lldb-dev wrote: > > Hi Folks, > > > > Is their a developer switch or diagnostic switch, that we can set in > > ll