[Lldb-commits] [lldb] r182060 - the return False in breakpoint actions should also be mentioned on the website

[Enrico Granata]

Author: enrico
Date: Thu May 16 18:17:25 2013
New Revision: 182060

URL: http://llvm.org/viewvc/llvm-project?rev=182060&view=rev
Log:
the return False in breakpoint actions should also be mentioned on the website


Modified:
    lldb/trunk/www/python-reference.html

Modified: lldb/trunk/www/python-reference.html
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/www/python-reference.html?rev=182060&r1=182059&r2=182060&view=diff
==============================================================================
--- lldb/trunk/www/python-reference.html (original)
+++ lldb/trunk/www/python-reference.html Thu May 16 18:17:25 2013
@@ -271,6 +271,10 @@ frame #0: 0x0000000100000bb6 a.out main
                         </td>
                     </tr>
                     </table>
+             <p>Optionally, a Python breakpoint command can return a value. Returning False tells LLDB that you do not want to stop at the breakpoint.
+                Any other return value (including None or leaving out the return statement altogether) is akin to telling LLDB to actually stop at the breakpoint.
+                This can be useful in situations where a breakpoint only needs to stop the process when certain conditions are met, and you do not want to inspect the
+                program state manually at every stop and then continue.
              <p>An example will show how simple it is to write some python code and attach it to a breakpoint. 
                 The following example will allow you to track the order in which the functions in a given shared library 
                 are first executed during one run of your program.  This is a simple method to gather an order file which