[Python-Dev] pdb enhancements (patch 896011, bugs 751124,875404) (original) (raw)

Ilya Sandler ilya at bluefir.net
Mon Mar 15 11:08:35 EST 2004

Hello,

Would it be possible for someone to review pdb enhancement patch #896011? (it has been sitting in the system for more than a month now)

In addition to providing functionality suggested earlier, it also addresses 2/3 of bug #751124...

I could also provide a patch for another pdb bug #875404 (but would like first to know the outcome for 896011)

Many thanks,

Ilya

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

* Previous message: [Python-Dev] pdb enhancements

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 > (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 it all the debugging settings (like breakpoints) this seems very inconvenient

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 (you 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.

Thanks,

Ilya PS. I am new on this list and can only hope that the questions are appropriate for python-dev

PS. Use the SF patch manager for submitting patches. Read http://python.org/dev/.

--Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list