[Python-Dev] could someone review pdb patch 896011?

Ilya Sandler ilya at bluefir.net
Sat Jun 19 00:38:22 EDT 2004

Would it be possible for someone to review patch 896011?
(it has been sitting in CVS without any feedback for about 4 months now)

The patch fixes a few minor bugs in pdb and implements a couple small (but
I think  useful features--like auto-restart, auto post-mortem modes)

The patch also fixes 2/3 of a bug#751124,

There are a couple more pdb bugs which I think I could fix, but I'd like
to  wait until I know the fate of the earlier patch.

Many thanks,


Guido van Rossum guido at python.org
Fri Feb 6 00:04:28 EST 2004

> I was wondering whether I should submit a formal patch for the
> following pdb enhancements:
> 1) right now if you do "pdb script"
> pdb will stop with a confusing
> > <string>(1)?()
> and you need to execute "s" before you get to the actual source being
> debugged, this seems somewhat unexpected and inconvenient
> A better way would be to go straight to the 1st line of user's code

If you can fix that, it would be great.  Just make sure that the fix
doesn't break anything else.

> 2) right now when the script exits, the debugger exits too, taking with
> all the debugging settings (like breakpoints) this seems very
> Basically the cost of a too early exit is high (as you lose your
> breakpoints) while the cost of not exiting debugger at all is minimal
> just need to press Ctrl-D to exit when you need it)
> So I would think that pdb should not exit on script's exit.
> (and, say, gdb does not exit when program exits...)
> Do these suggestions make sense? Is implementing them likely to break
> anything else?

Ditto.  I don't know what it would break, but you will hve to test
this thoroughly.

More information about the Python-Dev mailing list