summaryrefslogtreecommitdiffstats
path: root/lldb/source/Target/ThreadPlanCallFunction.cpp
diff options
context:
space:
mode:
authorEnrico Granata <granata.enrico@gmail.com>2011-07-19 18:03:25 +0000
committerEnrico Granata <granata.enrico@gmail.com>2011-07-19 18:03:25 +0000
commit20edcdbe8a267924e19646374cbead05ec9ea027 (patch)
tree9fa2db828ee6766299dde760d07431b4602c2423 /lldb/source/Target/ThreadPlanCallFunction.cpp
parent33824e572253bcb491a7e0d2a09a7f857f259f34 (diff)
downloadbcm5719-llvm-20edcdbe8a267924e19646374cbead05ec9ea027.tar.gz
bcm5719-llvm-20edcdbe8a267924e19646374cbead05ec9ea027.zip
The implementation of categories is now synchronization safe
Code cleanup: - The Format Manager implementation is now split between two files: FormatClasses.{h|cpp} where the actual formatter classes (ValueFormat, SummaryFormat, ...) are implemented and FormatManager.{h|cpp} where the infrastructure classes (FormatNavigator, FormatManager, ...) are contained. The wrapper code always remains in Debugger.{h|cpp} - Several leftover fields, methods and comments from previous design choices have been removed type category subcommands (enable, disable, delete) now can take a list of category names as input - for type category enable, saying "enable A B C" is the same as saying enable C enable B enable A (the ordering is relevant in enabling categories, and it is expected that a user typing enable A B C wants to look into category A, then into B, then into C and not the other way round) - for the other two commands, the order is not really relevant (however, the same inverted ordering is used for consistency) llvm-svn: 135494
Diffstat (limited to 'lldb/source/Target/ThreadPlanCallFunction.cpp')
-rw-r--r--lldb/source/Target/ThreadPlanCallFunction.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/source/Target/ThreadPlanCallFunction.cpp b/lldb/source/Target/ThreadPlanCallFunction.cpp
index 163322a661a..07608726908 100644
--- a/lldb/source/Target/ThreadPlanCallFunction.cpp
+++ b/lldb/source/Target/ThreadPlanCallFunction.cpp
@@ -339,7 +339,7 @@ ThreadPlanCallFunction::PlanExplainsStop ()
// If our subplan knows why we stopped, even if it's done (which would forward the question to us)
// we answer yes.
- if(m_subplan_sp.get() != NULL && m_subplan_sp->PlanExplainsStop())
+ if (m_subplan_sp.get() != NULL && m_subplan_sp->PlanExplainsStop())
return true;
// Check if the breakpoint is one of ours.
OpenPOWER on IntegriCloud