From: Khoo Yit Phang <khooyp@cs.umd.edu>
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: Tue, 10 Jan 2012 22:09:00 -0000 [thread overview]
Message-ID: <C3D2B5DC-CA57-4397-8FB8-B275302C7079@cs.umd.edu> (raw)
In-Reply-To: <CADPb22S9PXm67VCWSDMJLd1YFe9biGq1PiP-p0wUysXyQ_49-w@mail.gmail.com>
Hi,
On Jan 10, 2012, at 4:46 PM, Doug Evans wrote:
> On Tue, Jan 10, 2012 at 1:29 PM, Khoo Yit Phang <khooyp@cs.umd.edu> wrote:
>>
>> There's one caveat: if an inferior is running via, e.g., gdb.execute("run"), SIGINT will interrupt the inferior but not the enclosing "python" command. I think it would be better to also interrupt the "python" command, but I'm not sure how to detect this case yet.
>
> There is value in having the SIGINT *only* affect the inferior.
> It's up to the script to handle the various reasons why the inferior
> may have stopped, and you don't (generally) want to interfere with
> that (by interrupting the script too).
That makes sense, and I believe it's currently possible to detect that from Python via gdb.events.stop. It might be nicer to throw a custom exception (perhaps a subclass of KeyboardInterrupt), though that can be a different patch.
Yit
January 10, 2012
next prev parent reply other threads:[~2012-01-10 22:00 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 [this message]
2012-01-11 20:59 ` Tom Tromey
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=C3D2B5DC-CA57-4397-8FB8-B275302C7079@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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