This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author isandler
Recipients isandler
Date 2009-10-31.19:37:53
SpamBayes Score 0.0026339605
Marked as misclassified No
Message-id <1257017877.16.0.972733875092.issue7245@psf.upfronthosting.co.za>
In-reply-to
Content
Currently, pressing Ctrl-C in pdb will terminate the program and throw
the user into post-mortem debugging.

Other debuggers (e.g gdb and pydb) treat Ctrl-C differently: Ctrl-C only
stops the program and the user can resume it if needed. 

I believe current pdb behavior is user-unfriendly (as wanting to stop
and then resume the execution is a very common use case which is not
supported by pdb at all (I think)).


The attached patch changes pdb's Ctrl-C behavior to match
gdb's: Ctrl-C will stop the program and the user can resume the
execution later.
History
Date User Action Args
2009-10-31 19:37:57isandlersetrecipients: + isandler
2009-10-31 19:37:57isandlersetmessageid: <1257017877.16.0.972733875092.issue7245@psf.upfronthosting.co.za>
2009-10-31 19:37:55isandlerlinkissue7245 messages
2009-10-31 19:37:53isandlercreate