1.6 Files making up the Debugger

Here are the files making up the debugger and what is in them. Currently we use GNU automake in the build process, and this allows for substitution to take place in the files and Python programs which get installed. In particular the path to the Python interpreter is used that the debugger configured and tested with. A file with a .in suffix is a file that is the input for the substitution. The corresponding output file has the .in stripped off. For example pydb.py.in becomes pydb.py after a Python interpreter and package name (pydb) is substituted inside it.

pydb.py.in

Python debugger. Contains user-callable routines, e.g. run, debugger, runeval.

display.py

Classes to support gdb-like display/undisplay for pydb, the Extended Python debugger. Class Display and DisplayNode are defined.

fns.py

Functions to support the Debugger.

gdb.py.in

Handles gdb-like command processing.

info.py

Info subcommands. (Well, most of them).

pydbbdb.py

Routines here have to do with the subclassing of bdb. Defines Python debugger Basic Debugger (Bdb) class. This file could/should probably get merged into bdb.py

pydbcmd.py

Routines here have to do with parsing or processing commands, generally (but not always) they are not specific to pydb. They are sort of more oriented towards any gdb-like debugger. Also routines that need to be changed from cmd are here.

set.py

Set subcommands. (Well, most of them).

show.py

Show subcommands. (Well, most of them).

sighandler.py

Classes and routines which help in signal handling. Of the classes there is a signal handler manager class, SignalManager, and a class that is used by the signal handler that the program sees, SigHandler.

subcmd.py

Implements a sub-command class for handling info, set, and show subcommand processing.

threaddbg.py

Implements thread debugging.

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