Re: Handle SIGINT in Python

[Doug Evans <dje@google.com>]

On Wed, Jan 11, 2012 at 12:55 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> There is value in having the SIGINT *only* affect the inferior.
> Doug> It's up to the script to handle the various reasons why the inferior
> Doug> may have stopped, and you don't (generally) want to interfere with
> Doug> that (by interrupting the script too).
>
> I think Python code should have to request something like this
> specially.  The scripting case is less usual than the interactive
> debugging (perhaps with some Python helper code) case.  I think it would
> be weird for the behavior the user sees, by default, to depend on
> whether Python or GDB code was active at the moment of C-c.

I'm not sure we're talking about the same thing.
I wasn't suggesting the behaviour be different depending on whether
GDB or Python was running.
[For reference sake, to make sure we're on the same page, my comment
is solely for the case where the inferior is launched by gdb, the
inferior is running, has the terminal, and will get the SIGINT.]

> That is, a C-c when processing a 'python' command in a breakpoint's
> 'commands' list should have the same general effect as if we were
> processing any other command.

PTAL.