From a647712f167e6dffc6439c6a1ac412386515466f Mon Sep 17 00:00:00 2001 From: Mark Florisson Date: Sat, 13 Nov 2010 12:39:11 +0100 Subject: [PATCH] Document 'cy finish' and 'cy select' --- src/userguide/debugging.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/userguide/debugging.rst b/src/userguide/debugging.rst index 79ad225f..0daec834 100644 --- 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 -- 2.26.2