From c60b6eadecb2d41c7b7d4661dbffedff764ca8d1 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Tue, 8 Jul 2014 19:27:35 +0000 Subject: Document the "thread.completed-expression" feature in the "expression" command help. llvm-svn: 212558 --- lldb/source/Commands/CommandObjectExpression.cpp | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'lldb/source/Commands/CommandObjectExpression.cpp') diff --git a/lldb/source/Commands/CommandObjectExpression.cpp b/lldb/source/Commands/CommandObjectExpression.cpp index 4a92f489ae0d..29e6f87cbfd0 100644 --- a/lldb/source/Commands/CommandObjectExpression.cpp +++ b/lldb/source/Commands/CommandObjectExpression.cpp @@ -218,6 +218,15 @@ User defined variables:\n\ your user defined variable is a $, then the variable's value will be available in future\n\ expressions, otherwise it will just be available in the current expression.\n\ \n\ +\n\ +Continuing evaluation after a breakpoint:\n\ + If the \"-i false\" option is used, and execution is interrupted by a breakpoint hit, once\n\ + you are done with your investigation, you can either remove the expression execution frames\n\ + from the stack with \"thread return -x\" or if you are still interested in the expression result\n\ + you can issue the \"continue\" command and the expression evaluation will complete and the\n\ + expression result will be available using the \"thread.completed-expression\" key in the thread\n\ + format.\n\ +\n\ Examples: \n\ \n\ expr my_struct->a = my_array[3] \n\ -- cgit v1.2.3