public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "khooyp at cs dot umd.edu" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/13265] SIGINT handling
Date: Tue, 10 Jan 2012 01:04:00 -0000	[thread overview]
Message-ID: <bug-13265-4717-jwTVcqo648@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13265-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13265

--- Comment #1 from Khoo Yit Phang <khooyp at cs dot umd.edu> 2012-01-10 01:03:14 UTC ---
Created attachment 6156
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6156
Patch to allow SIGINT to interrupt the "python" command.

I've attached a patch that allows SIGINT to interrupt a "python" command. It
works by installing a Python-specific SIGINT handler just before executing a
Python script, and restoring the original SIGINT handler after execution as
well as at calls to gdb.execute(...).

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.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  reply	other threads:[~2012-01-10  1:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 17:36 [Bug python/13265] New: " tromey at redhat dot com
2012-01-10  1:04 ` khooyp at cs dot umd.edu [this message]
2012-01-10  1:08 ` [Bug python/13265] " khooyp at cs dot umd.edu
2012-01-10 20:53 ` tromey at redhat dot com
2012-01-10 21:06 ` khooyp at cs dot umd.edu
2012-01-10 21:18 ` khooyp at cs dot umd.edu
2013-01-11 16:39 ` tromey at redhat dot com

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=bug-13265-4717-jwTVcqo648@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).