Hi jingham,
Expect stop reason watchpoint for the step over breakpoint thread plan
Some kernel report a hardware watchpoint hit trap after a single step operation
instead of a trace operation.
http://reviews.llvm.org/D8081
Files:
source/Target/ThreadPlanStepOverBreakpoint.cpp
Index: source/Target/ThreadPlanStepOverBreakpoint.cpp
===================================================================
--- source/Target/ThreadPlanStepOverBreakpoint.cpp
+++ source/Target/ThreadPlanStepOverBreakpoint.cpp
@@ -76,6 +76,8 @@
{
case eStopReasonTrace:
case eStopReasonNone:
+ // Some kernel reports the stop reason for a single step request as a
hit of a hardware watchpoint
+ case eStopReasonWatchpoint:
return true;
case eStopReasonBreakpoint:
// It's a little surprising that we stop here for a breakpoint
hit. However, when you single step ONTO a
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
Index: source/Target/ThreadPlanStepOverBreakpoint.cpp
===================================================================
--- source/Target/ThreadPlanStepOverBreakpoint.cpp
+++ source/Target/ThreadPlanStepOverBreakpoint.cpp
@@ -76,6 +76,8 @@
{
case eStopReasonTrace:
case eStopReasonNone:
+ // Some kernel reports the stop reason for a single step request as a hit of a hardware watchpoint
+ case eStopReasonWatchpoint:
return true;
case eStopReasonBreakpoint:
// It's a little surprising that we stop here for a breakpoint hit. However, when you single step ONTO a
_______________________________________________
lldb-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits