From f5f560caea6a5288aef93b6110421777357f0920 Mon Sep 17 00:00:00 2001 From: Enrico Granata Date: Thu, 16 May 2013 23:09:09 +0000 Subject: Note in the documentation about the fact that Python callbacks can return a value and if that value is False, LLDB won’t stop at the breakpoint MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit llvm-svn: 182059 --- lldb/source/Commands/CommandObjectBreakpointCommand.cpp | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'lldb/source/Commands/CommandObjectBreakpointCommand.cpp') diff --git a/lldb/source/Commands/CommandObjectBreakpointCommand.cpp b/lldb/source/Commands/CommandObjectBreakpointCommand.cpp index 3dbb6e052d5..c4504a4c651 100644 --- a/lldb/source/Commands/CommandObjectBreakpointCommand.cpp +++ b/lldb/source/Commands/CommandObjectBreakpointCommand.cpp @@ -167,6 +167,12 @@ initialized:\n\ (lldb)\n\ \n\ \n\ +Your Python code, however organized, can optionally return a value.\n\ +If the returned value is False, that tells LLDB not to stop at the breakpoint\n\ +to which the code is associated. Returning anything other than False, or even\n\ +returning None, or even omitting a return statement entirely, will cause\n\ +LLDB to stop.\n\ +\n\ Final Note: If you get a warning that no breakpoint command was generated, but\n\ you did not get any syntax errors, you probably forgot to add a call to your\n\ functions.\n\ -- cgit v1.2.3