From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23014 invoked by alias); 10 Jan 2012 21:06:40 -0000 Received: (qmail 22992 invoked by uid 22791); 10 Jan 2012 21:06:34 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 10 Jan 2012 21:06:22 +0000 From: "khooyp at cs dot umd.edu" To: gdb-prs@sourceware.org Subject: [Bug python/13265] SIGINT handling Date: Tue, 10 Jan 2012 21:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: khooyp at cs dot umd.edu X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2012-q1/txt/msg00032.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=13265 --- Comment #3 from Khoo Yit Phang 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.