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 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
ne 28, 2019 6:16 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 ea
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()
>
>>> On Jun 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-
s to
>>> take a stab at making 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
t;>>> broadly and were waiting for some more interest to spend time cleaning it
>>>> up and writing tests, etc. Then years passed... So it is not entirely
>>>> surprising that the facility needs some attention. If somebody wants to
>>>> take a st
>>>>> only instruction 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
;t think they would do what Vangelis wants. He
>>>>>> would have to drive the debugger with only the step-instruction command,
>>>>>> which I think qualifies as interfering with stepping.
>>>>>>
>>>>>> The ThreadPlanTracer
mit this patch for review?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On 28 Jun 2019, at 20:50, Jim Ingham wrote:
>>>>>>>
>>>>>>> Stop hooks only trigger when cont
10 matches
Mail list logo