hanchenye-llvm-project/lldb/source/Breakpoint
Jim Ingham ff7ac6a7b9 Breakpoint conditions were making result variables, which they should not do.
The result variables aren't useful, and if you have a breakpoint on a
common function you can generate a lot of these.  So I changed the
code that checks the condition to set ResultVariableIsInternal in the
EvaluateExpressionOptions that we pass to the execution.
Unfortunately, the check for this variable was done in the wrong place
(the static UserExpression::Evaluate) which is not how breakpoint
conditions execute expressions (UserExpression::Execute).  So I moved
the check to UserExpression::Execute (which Evaluate also calls) and made the
overridden method DoExecute.

llvm-svn: 266093
2016-04-12 17:17:35 +00:00
..
Breakpoint.cpp Make the Language print the description of the Exception Breakpoint resolver. Also 2015-12-18 02:14:04 +00:00
BreakpointID.cpp
BreakpointIDList.cpp
BreakpointList.cpp
BreakpointLocation.cpp Breakpoint conditions were making result variables, which they should not do. 2016-04-12 17:17:35 +00:00
BreakpointLocationCollection.cpp
BreakpointLocationList.cpp
BreakpointOptions.cpp
BreakpointResolver.cpp Add an "offset" option to "break set -n" and "break set -f -l". 2016-03-09 18:59:13 +00:00
BreakpointResolverAddress.cpp Add an "offset" option to "break set -n" and "break set -f -l". 2016-03-09 18:59:13 +00:00
BreakpointResolverFileLine.cpp Add an "offset" option to "break set -n" and "break set -f -l". 2016-03-09 18:59:13 +00:00
BreakpointResolverFileRegex.cpp
BreakpointResolverName.cpp Add an "offset" option to "break set -n" and "break set -f -l". 2016-03-09 18:59:13 +00:00
BreakpointSite.cpp
BreakpointSiteList.cpp
CMakeLists.txt
Stoppoint.cpp
StoppointCallbackContext.cpp
StoppointLocation.cpp
Watchpoint.cpp
WatchpointList.cpp Fix watchpoint check to use watchpoint ranges 2015-12-07 19:38:58 +00:00
WatchpointOptions.cpp