summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/MacOSX-Kernel/CommunicationKDP.cpp
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2016-04-06 09:10:29 +0000
committerPavel Labath <labath@google.com>2016-04-06 09:10:29 +0000
commit3ce324af6b8df4be38c09e4fb571f7c99a9dc776 (patch)
tree43d7d8fb817e93d2cdd374e1ee7591a418126683 /lldb/source/Plugins/Process/MacOSX-Kernel/CommunicationKDP.cpp
parenta95e0effc01d0eb124c489058ae30922c8a5508d (diff)
downloadbcm5719-llvm-3ce324af6b8df4be38c09e4fb571f7c99a9dc776.tar.gz
bcm5719-llvm-3ce324af6b8df4be38c09e4fb571f7c99a9dc776.zip
Fix a cornercase in breakpoint reporting
Summary: This resolves a similar problem as D16720 (which handled the case when we single-step onto a breakpoint), but this one deals with involutary stops: when we stop a thread (e.g. because another thread has hit a breakpont and we are doing a full stop), we can end up stopping it right before it executes a breakpoint instruction. In this case, the stop reason will be empty, but we will still step over the breakpoint when do the next resume, thereby missing a breakpoint hit. I have observed this happening in TestConcurrentEvents, but I have no idea how to reproduce this behavior more reliably. Reviewers: clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D18692 llvm-svn: 265525
Diffstat (limited to 'lldb/source/Plugins/Process/MacOSX-Kernel/CommunicationKDP.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud