1.2.14.3 Thread Extensions to the frame and break commands

1.2.14.3 Thread Extensions to the `frame` and `break` commands

When thread debugging is turned on, a couple of normal pydb commands allow for a thread name to be indicated. In particular, you can specify whether or not a breakpoint should occur at a point across all threads or only on a specific thread.

For commands that take a thread name, you can use a dot (.) to indicate the current frame.

And if Python version 2.5 or greater is installed or threadframe with an older version of Python is installed, you can inspect and change local variables from other thread frames via an expanded frame command.

Note that the next and step commands do not guarantee you will remain in the same thread. In particular step stops at the next Python statement to be executed whichever thread that might be.

There is currently a bug in next in that it is possible it may act like step if occasionally.

frame [thread-name|thread-number] [frame-number]

Move the current frame to the frame frame-number if specified, or the current frame, 0 if no frame number specified.

Move the current frame to the specified frame number. If a thread-Name or thread-numberis given, move the current frame to that. A dot (.) can be used to indicate the name of the current frame.

b(reak) [[filename:]lineno|function [thread thread-name] [, condition]]

See 1.2.4. If a specific thread name is given then a breakpoint will occur only when in that thread. A dot (.) can be used to indicate the name of the current frame.

tbreak [[filename:]lineno|function [thread thread-name][, condition]]

See 1.2.4. If a specific thread name is given then a breakpoint will occur only when in that thread. A dot (.) can be used to indicate the name of the current frame.

See About this document... for information on suggesting changes.