Thanks a lot Jim.
Our motivation was from the idea that the user might not be knowing which
variable might be causing the issue and might need multiple runs to finally
zero upon the problem. Another one is if the variable in question is
updated inside a loop. here we need not track all updates, ju
BTW, if you do want to follow this approach, then you should look at the
"thread plan tracer" bits built into lldb, if you haven't already seen them.
The idea is that you can inject an automatic tracer into the machinery that
governs how the program is executed. The tracer can either follow th
From what I can tell, you are suggesting using instruction single stepping and
printing out the variable value if it has changed. Is that right?
That seems much more expensive than watchpoints, and it isn't clear to me what
the benefits would be. I would be interested to hear more about the
