From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>, gdb-patches@sourceware.org
Subject: Re: Handle SIGINT in Python
Date: Wed, 11 Jan 2012 20:59:00 -0000 [thread overview]
Message-ID: <m38vle557m.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22S9PXm67VCWSDMJLd1YFe9biGq1PiP-p0wUysXyQ_49-w@mail.gmail.com> (Doug Evans's message of "Tue, 10 Jan 2012 13:46:31 -0800")
>>>>> "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
next prev parent reply other threads:[~2012-01-11 20:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 21:31 Khoo Yit Phang
2012-01-10 21:47 ` Doug Evans
2012-01-10 22:09 ` Khoo Yit Phang
2012-01-11 20:59 ` Tom Tromey [this message]
2012-01-11 21:06 ` Paul_Koning
2012-01-11 21:23 ` Tom Tromey
2012-01-12 0:54 ` Doug Evans
2012-01-12 15:52 ` Kevin Pouget
2012-01-12 16:48 ` Paul_Koning
2012-01-13 10:55 ` Kevin Pouget
2012-01-13 12:11 ` Paul_Koning
2012-01-10 21:49 ` Tom Tromey
2012-01-11 21:15 ` Tom Tromey
2012-01-11 21:49 ` Khoo Yit Phang
2012-01-11 22:46 ` Khoo Yit Phang
2012-01-20 21:40 ` Tom Tromey
2012-01-22 16:36 ` Khoo Yit Phang
2012-01-22 20:54 ` Khoo Yit Phang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38vle557m.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=khooyp@cs.umd.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox