aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineCopyPropagation.cpp
diff options
context:
space:
mode:
authorJason Molenda <jmolenda@apple.com>2024-09-13 09:04:28 -0700
committerGitHub <noreply@github.com>2024-09-13 09:04:28 -0700
commit65a4d11b1e67429d53df1fcee0f93492aa95c448 (patch)
treef938ac92bff52f263fab72bb339a33e8d44ab253 /llvm/lib/CodeGen/MachineCopyPropagation.cpp
parent213c59ddd2a702ddd3d849cea250440b1ed718e0 (diff)
downloadllvm-65a4d11b1e67429d53df1fcee0f93492aa95c448.zip
llvm-65a4d11b1e67429d53df1fcee0f93492aa95c448.tar.gz
llvm-65a4d11b1e67429d53df1fcee0f93492aa95c448.tar.bz2
[lldb] Set the stop reason when receiving swbreak/hwbreak (#108518)
xusheng added support for swbreak/hwbreak a month ago, and no special support was needed in ProcessGDBRemote when they're received because lldb already marks a thread as having hit a breakpoint when it stops at a breakpoint site. However, with changes I am working on, we need to know the real stop reason a thread stopped or the breakpoint hit will not be recognized. This is similar to how lldb processes the "watch/rwatch/awatch" keys in a thread stop packet -- we set the `reason` to `watchpoint`, and these set it to `breakpoint` so we set the stop reason correctly later in these methods.
Diffstat (limited to 'llvm/lib/CodeGen/MachineCopyPropagation.cpp')
0 files changed, 0 insertions, 0 deletions