Document 'cy finish' and 'cy select'

diff --git a/src/userguide/debugging.rst b/src/userguide/debugging.rst
index 79ad225fdc8207034e064262a3fe5fb5b9e0f4d7..0daec834950d5a15ec154350f1ae18451e97f85b 100644 (file)
--- a/src/userguide/debugging.rst
+++ b/src/userguide/debugging.rst
@@ -133,12 +133,23 @@ of these commands are analogous to their respective gdb command.
 
     Go up and down the stack to what is considered a relevant frame.
 
+.. function:: cy finish
+
+    Execute until an upward relevant frame is met or something halts 
+    execution.
+
 .. function:: cy bt
               cy backtrace
 
     Print a traceback of all frames considered relevant. The ``-a`` option
     makes it print the full traceback (all C frames).
 
+.. function:: cy select
+
+    Select a stack frame by number as listed by ``cy backtrace``. This
+    command is introduced because ``cy backtrace`` prints a reversed stack
+    trace, so frame numbers differ from gdb's ``bt``.
+
 .. function:: cy print varname
 
     Print a local or global Cython, Python or C variable (depending on the