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 21:06:00 -0000	[thread overview]
Message-ID: <bug-13265-4717-aHKivMahjO@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 #3 from Khoo Yit Phang <khooyp at cs dot umd.edu> 2012-01-10 21:06:18 UTC ---
Thanks for the tip: I'll post to gdb-patches with a link back here.

As for the cleanup-creating function (gdbpy_suspend_sigint_handler), note that
when it calls gdbpy_resume_sigint_handler, it does not restore the original
SIGINT handler but whatever SIGINT handler that is installed at cleanup. The
idea was that, if some nested function call changes the SIGINT handler, that
should be propagated back down the call stack as well. As it is, I don't know
whether the SIGINT handler is ever changed under normal operation, so there
won't be any observable difference in behavior between my implementation and
your suggestion.

I'll update my patch with a comment to explain the above in a moment.

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


  parent reply	other threads:[~2012-01-10 21:06 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 ` [Bug python/13265] " khooyp at cs dot umd.edu
2012-01-10  1:08 ` 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 [this message]
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-aHKivMahjO@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).