This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Handle SIGINT in Python


>>>>> "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.

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.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]