Ilya Sandler <ilya.sand...@gmail.com> added the comment:
Here is a list of Ctrl-C scenarios: ("current" below means the prepatch version
of pdb).
1. program is running (last command was "c", "n", etc). Currently, Ctrl-C
throws debugger into postmortem. Desired behavior: interrupt the program. This
is the only scenario supported by the patch.
2. Program is stopped (debugger is interacting with the user). Currently,
Ctrl-C will throw debugger into postmortem. Desired behaviour: either ignore
Ctrl-C or abandon the current command (that's what gdb does).
3. Program is stopped and pdb runs one of the commands which catch exceptions
(e.g "p"). Currently, Ctrl-C will abort the command and return pdb to the
prompt. I think this behavior should be kept.
4. Program finished (debugger is in postmortem). Currently, Ctrl-C will quit
the debugger. Desired behavior: either ignore Ctrl-C or abandon the current
command.
Essentially, I think the best behavior is to have Ctrl-C to interrupt whatever
pdb is doing and return to the fresh prompt.
I am assuming that behavior on Windows and Linux should be identical/nearly
identical.
Does the above list make sense?
I would greatly appreciate any feedback/comments/guidance/etc.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue7245>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
