From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-11194-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 17037 invoked by alias); 10 Jan 2012 20:53:15 -0000
Received: (qmail 17018 invoked by uid 22791); 10 Jan 2012 20:53:13 -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 20:53:02 +0000
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/13265] SIGINT handling
Date: Tue, 10 Jan 2012 20:53: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: tromey at redhat dot com
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: <bug-13265-4717-dtuNW98vHD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-13265-4717@http.sourceware.org/bugzilla/>
References: <bug-13265-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2012-q1/txt/msg00031.txt.bz2

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

--- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-01-10 20:52:18 UTC ---
For a real review you would have to email to gdb-patches.

I think the cleanup-creating function should pass the old
signal handler as an argument to the cleanup function.
That way you can stack them without dealing with the
calls to gdbpy_restore_sigint_handler when making a cleanup.

I haven't looked into this area of gdb much; so I don't know
what to suggest about interrupting Python while the inferior
is running.

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