aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2022-07-12 18:34:24 -0700
committerJim Ingham <jingham@apple.com>2022-07-18 14:36:32 -0700
commit5778ada8e54edb2bc2869505b88a959d1915c02f (patch)
treeb8c36bc422776517dd2bc5c74a67db43f4cbe4b1 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
parent8d0383eb694e13a999c9c95adc4b56771429e551 (diff)
downloadllvm-5778ada8e54edb2bc2869505b88a959d1915c02f.zip
llvm-5778ada8e54edb2bc2869505b88a959d1915c02f.tar.gz
llvm-5778ada8e54edb2bc2869505b88a959d1915c02f.tar.bz2
Make hit point counts reliable for architectures that stop before evaluation.
Since we want to present the "new & old" values for watchpoint hits, on architectures, including the ARM family, that stop before the triggering instruction is run, we need to single step over the instruction before stopping for realz. This was incorrectly done directly in the StopInfoWatchpoint::ShouldStop. That causes problems if more than one thread stops "for a reason" at the same time as the watchpoint, since the other actions didn't expect the process to make progress in this part of the execution control machinery. The correct way to do this is to schedule the step over using ThreadPlans, and then to restore the stop info after that plan stops, so that the rest of the stop info actions can happen when all the other threads have handled their immediate actions as well. Differential Revision: https://reviews.llvm.org/D129814
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions