Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> On 28 Jun 2019, at 20:50, Jim Ingham wrote: >>>>>>> >>>>>>> Stop hooks only trigger when control is about to be returned to t

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

s wants. He >>>>>> would have to drive the debugger with only the step-instruction command, >>>>>> which I think qualifies as interfering with stepping. >>>>>> >>>>>> The ThreadPlanTracer is really the ticket, it does forc

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

struction single step when it is realizing the more complex >>>>> stepping operations, and then has hooks on each instruction stop. >>>>> >>>>> Sean and I added this facility way way back in the early days of lldb >>>>> because w

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

>>>> Sean and I added this facility way way back in the early days of lldb >>>> because we needed it to figure out some problems with the expression >>>> parser. We weren't really sure whether we were going to promote it more >>>> broadly and were wai

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

aking this work reliably again, that would be awesome! >>> >>> Jim >>> >>> >>> >>>> On Jun 28, 2019, at 7:09 AM, Ted Woodward via lldb-dev >>>> wrote: >>>> >>>> You want to set up a stop-hook. >&

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

28, 2019, at 7:09 AM, Ted Woodward via lldb-dev >>> wrote: >>> >>> You want to set up a stop-hook. >>> >>> See “help target stop-hook”, specifically “help target stop-hook add”. >>> >>> target stop-hook add -o “register rea

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

Thank you very much for your replies! I took a look at ThreadPlanTracer and found out that the crash reason was the call of a virtual method during object construction:virtual Process.UpdateThreadList()└── ProcessGDBRemote.UpdateThreadList()    └── new ThreadGDBRemote()        └── new Thread()     

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

6 AM > To: via lldb-dev > Cc: Vangelis Tsiatsianas > Subject: [EXT] [lldb-dev] Enabling single-step mode and acting on each > executed instruction > > Hello, > > I would like to set the target in single-step mode and perform an action > right after each instruction

Re: [lldb-dev] Enabling single-step mode and acting on each executed instruction

To: via lldb-dev Cc: Vangelis Tsiatsianas Subject: [EXT] [lldb-dev] Enabling single-step mode and acting on each executed instruction Hello, I would like to set the target in single-step mode and perform an action right after each instruction is executed. Notably, it is crucial to do so

[lldb-dev] Enabling single-step mode and acting on each executed instruction

Hello, I would like to set the target in single-step mode and perform an action right after each instruction is executed. Notably, it is crucial to do so transparently, i.e. without interfering with user breakpoints, watchpoints, stepping etc.. Could you provide me with some guidance on how