Advanced Python Debugging with PDB

The Python Debugger (PDB) is an invaluable tool for diagnosing and resolving issues in Python applications. It allows developers to execute code step by step, inspect variables, and evaluate expressions interactively. By providing deep insights into program execution, PDB facilitates the identification and correction of complex bugs.

Getting Started with PDB

To initiate a debugging session within your code, insert the following line at the desired starting point:

import pdb; pdb.set_trace()
    

This sets a breakpoint in your code, and when execution reaches this point, the PDB interactive console opens.

Alternatively, you can run your script through PDB using the command line:

python -m pdb my_script.py
    

This starts the debugger at the beginning of your script.

Basic PDB Commands

Once inside the PDB console, you can use various commands to navigate and inspect your code:

  • list (l): Show the current location in the code.
    (Pdb) l
        
  • next (n): Execute the next line without stepping into functions.
    (Pdb) n
        
  • step (s): Step into the function call at the current line.
    (Pdb) s
        
  • continue (c): Continue execution until the next breakpoint.
    (Pdb) c
        
  • print (p): Print the value of an expression.
    (Pdb) p variable_name
        
  • quit (q): Exit the debugger and terminate the program.
    (Pdb) q
        

Advanced Debugging Techniques

PDB offers advanced features to further refine the debugging process:

See also  Building Simple Neural Networks with Python

Setting Breakpoints

You can set breakpoints at specific lines or functions:

(Pdb) break my_script.py:25  # Set breakpoint at line 25
    (Pdb) break my_function  # Set breakpoint at the start of 'my_function'
    

Conditional Breakpoints

Set breakpoints that activate only when certain conditions are met:

(Pdb) break my_script.py:30, x > 10
    

This breakpoint will only pause execution at line 30 if x > 10.

Inspecting the Call Stack

Use the where (w) command to display the call stack and understand how the current execution point was reached:

See also  Troubleshooting Paramiko SFTP Server Connection Drops

(Pdb) where
    

Examining and Modifying Variables

Inspect variables and even modify them on the fly:

(Pdb) p my_variable
    (Pdb) my_variable = 42
    

Executing Arbitrary Code

Run any Python code within the debugger to test hypotheses or inspect data structures:

(Pdb) !result = compute_value(x, y)
    (Pdb) p result
    

The ! tells PDB to execute the line as Python code.

Continuing Execution

Use until (unt) to continue execution until a line greater than the current one is reached:

(Pdb) unt
    

This is useful in loops to move forward without stepping through each iteration.

Integrating PDB into Your Workflow

Incorporate PDB into your development process for more efficient debugging:

  • Use Breakpoints Strategically: Place breakpoints at critical points in your code where issues are likely to occur.
  • Automate with pdb.set_trace(): Insert pdb.set_trace() directly into your code to start debugging at that point.
  • Debugging Tests: Use PDB in conjunction with testing frameworks like pytest:

    pytest --pdb
        

Example Debugging Session

Consider the following simple script with a bug:

See also  How to convert array to binary?

def divide(a, b):
        result = a / b
        return result
    
    x = 10
    y = 0
    print("Result:", divide(x, y))
    

Running this script raises a ZeroDivisionError. Let’s debug it with PDB:

python -m pdb my_script.py
    

In the PDB console:

(Pdb) n  # Step to the next line
(Pdb) n
(Pdb) s  # Step into the 'divide' function
(Pdb) p a  # Inspect variable 'a'
10
(Pdb) p b  # Inspect variable 'b'
0
(Pdb) p result  # Try to inspect 'result' before it's defined
*** NameError: name 'result' is not defined
(Pdb) n  # Execute the division
ZeroDivisionError: division by zero
> my_script.py(3)divide()
-> result = a / b
(Pdb) q  # Quit the debugger
    

Through this session, we identified that b is zero, causing the error.

Additional Resources