Alternatives in the command syntax are separated by a vertical barĮntering a blank line repeats the last command entered. Square brackets ( ) in the command syntax the square brackets must not be Separated by whitespace (spaces or tabs).
h(elp) means thatĮither h or help can be used to enter the help command (but not he Most commands can beĪbbreviated to one or two letters as indicated e.g. The commands recognized by the debugger are listed below. See the documentation for the functions explained above. run ( statement, globals = None, locals = None ) ¶ runeval ( expression, globals = None, locals = None ) ¶ runcall ( function, * args, ** kwds ) ¶ set_trace ( ) ¶ The readrc argument defaults to true and controls whether Pdb will loadĮxample call to enable tracing with skip:Ĭhanged in version 3.6: The readrc argument. Want Pdb not to touch the SIGINT handler, set nosigint to true. This allows you to break into the debugger again by pressing Ctrl- C. User presses Ctrl- C on the console) when you give a continue command. The debugger will not step into frames that originate in a moduleīy default, Pdb sets a handler for the SIGINT signal (which is sent when the The skip argument, if given, must be an iterable of glob-style module name Underlying cmd.Cmd class see the description there. The completekey, stdin and stdout arguments are passed to the Pdb ( completekey = 'tab', stdin = None, stdout = None, skip = None, nosigint = False, readrc = True ) ¶ If you want toĪccess further features, you have to do this yourself: class pdb. Pdb class and calling the method of the same name.
The run* functions and set_trace() are aliases for instantiating the Traceback is given, it uses the one of the exception that is currentlyīeing handled (an exception must be being handled if the default is to beĮnter post-mortem debugging of the traceback found in post_mortem ( traceback = None ) ¶Įnter post-mortem debugging of the given traceback object. Header is printed to the console just before debugging begins.Ĭhanged in version 3.7: The keyword-only argument header.
#Ef default command timeout code
This is useful to hard-codeĪ breakpoint at a given point in a program, even if the code is not set_trace ( *, header = None ) ¶Įnter the debugger at the calling stack frame. The debugger prompt appears as soon as the function
When runcall() returns, it returns whatever theįunction call returned. runcall ( function, * args, ** kwds ) ¶Ĭall the function (a function or method object, not a string) with the Otherwise this function is similar to run(). When runeval() returns, it returns the value of theĮxpression. runeval ( expression, globals = None, locals = None ) ¶Įvaluate the expression (given as a string or a code object) under debuggerĬontrol. (See the explanation of the built-inĮxec() or eval() functions.) pdb. The optional globals and locals arguments specify theĮnvironment in which the code is executed by default the dictionary of the Statement using step or next (all these commands areĮxplained below).
Set breakpoints and type continue, or you can step through the The debugger prompt appears before any code is executed you can run ( statement, globals = None, locals = None ) ¶Įxecute the statement (given as a string or a code object) under debuggerĬontrol. The module defines the following functions each enters the debugger in a > f ( 0 ) Traceback (most recent call last):įile "", line 2, in f ZeroDivisionError: division by zero > pdb. This failure occurred while attempting to connect to the routing destination.> import pdb > def f ( x ). The connection could have timed out while waiting for server to complete the login process and respond Or it could have timed out while attempting to create multiple active connections. The timeout period elapsed during the post-login phase.
0 kommentar(er)
