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

I will to do so, starting with bugs.llvm.org . Thank you! 🙂 ― Vangelis > On 2 Jul 2019, at 23:09, Jim Ingham wrote: > > > >> On Jul 2, 2019, at 11:52 AM, Vangelis Tsiatsianas >> wrote: >> >> I would like to leave it as a suggestion for the future, just in case the

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

> On Jul 2, 2019, at 11:52 AM, Vangelis Tsiatsianas > wrote: > > I would like to leave it as a suggestion for the future, just in case the > need for such a mechanism arises in other places within LLDB or for plugins. File an enhancement request with bugs.llvm.org, otherwise it will get lost

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

I would like to leave it as a suggestion for the future, just in case the need for such a mechanism arises in other places within LLDB or for plugins. Thank you, once again, for your time and very helpful responses! ― Vangelis > On 2 Jul 2019, at 02:16, Jim Ingham wrote: > > There isn't a

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

There isn't a general mechanism for external clients to watch settings changes. But IMO, it would be appropriate for the setter for the target.process.thread.trace-thread set function to go do this work. Having an explicit relationship between setting the setting and changing state in the thr

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

Thank you! I created the revision and added you as a reviewer (https://reviews.llvm.org/D64043 ). Regarding the callback mechanism, I was thinking more of components having the ability to express interest in a setting value (e.g. "target.process.thread.trace-thr

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

We use http://reviews.llvm.org Click on the Favorites:Differential side bar item, and then on Create Diff in the URH Corner of the window. If you make your diff with: svn diff --diff-cmd=diff -x -U99 or the git equivalent, then they are much easier to review. Once you have the diff, sele

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

Stop hooks only trigger when control is about to be returned to the user. And in its normal mode, lldb doesn't step instruction all the time anyway... So I don't think they would do what Vangelis wants. He would have to drive the debugger with only the step-instruction command, which I think

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

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 read pc” will read the pc each time the target stops. From: lldb-dev On Behalf Of Vangelis Tsiatsianas via lldb-dev Sent: Friday, June 28, 2019 6:16 AM To: v