Tom Tromey wrote a PythonGdb tutorial which helps make the [[http://sourceware.org/gdb/onlinedocs/gdb/Python.html|official Python binding docs]] much more accessible:

 1. [[http://tromey.com/blog/?p=494|Installing a Python-enabled debugger]]<<BR>>We’ll start at the very beginning: checking it out, building it, and then “hello, world”.
 1. [[http://tromey.com/blog/?p=501|Writing a new gdb command]]<<BR>>I'll show you how to implement a new command to save breakpoints to a file.
 1. [[http://tromey.com/blog/?p=515|gdb convenience functions]]<<BR>>Now we’ll see how to write new functions, so your Python code can be called during expression evaluation.
 1. [[http://tromey.com/blog/?p=520|Parameters, and extending require]]<<BR>>Parameters are a nice feature when you are polishing your gdb extensions for more general use. Having Python extensions which are themselves extensible - like require - is an emerging theme of python-gdb.
 1. [[http://tromey.com/blog/?p=522|The filtering backtrace]]<<BR>>Now let’s do something really useful. We’ve reimplemented backtrace, entirely in Python.  And, in so doing, we’ve added some functionality, namely filtering and reverse backtraces
 1. [[http://tromey.com/blog/?p=535|Auto-loading Python code]]<<BR>>Suppose someone writes a new filter - it would be nice to get it without having to edit anything. Naturally, we provide an automatic mechanism for loading code.
 1. [[http://tromey.com/blog/?p=524|Pretty printing, part 1]]<<BR>>You can register a pretty-printer class by matching the name of a type; any time gdb tries to print a value whose type matches that regular expression, your printer will be used instead.
 1. [[http://tromey.com/blog/?p=546|Pretty printing, part 2]]<<BR>>There are a few additions which are helpful with more complex data types.  This post will explain the other printer methods used by gdb, and will explain how pretty-printing interacts with MI, the gdb machine interface.
 1. [[http://tromey.com/blog/?p=548|Scripting gdb]]<<BR>>In this post I want to look at gdb from a different angle: as a library.  I’ve long thought it would be pretty useful to be able to use gdb as a kind of scriptable tool for messing around with running programs, or even just symbol tables and debug info; the Python work enables this.
 1. [[http://tromey.com/blog/?p=550|Wacky stuff]]<<BR>>What could be flashier than a GUI?
 1. [[http://tromey.com/blog/?p=552|The End]]<<BR>>What next? Now is an exciting time to be working on gdb.  There are a number of very interesting projects underway.
 1. [[http://tromey.com/blog/?p=696|Events]]<<BR>>Gdb's event system.
 1. [[http://tromey.com/blog/?p=698|Breakpoints]]<<BR>>API for handling breakpoints.
 1. [[http://www.cinsk.org/articles/gdb3.en.html|Adding new GDB Commands using Python]]<<BR>>Adding some useful commands (i.e. hexdump, iconv) to GDB