From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21693 invoked by alias); 22 Jan 2013 09:39:06 -0000 Received: (qmail 21670 invoked by uid 48); 22 Jan 2013 09:39:05 -0000 From: "m at bruenink dot de" To: gdb-prs@sourceware.org Subject: [Bug python/14674] No KeyboardInterrupt exception during gdb.execute Date: Tue, 22 Jan 2013 09:39: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: minor X-Bugzilla-Who: m at bruenink dot de 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" Content-Transfer-Encoding: quoted-printable 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: 2013-q1/txt/msg00106.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=3D14674 --- Comment #2 from Marc Br=C3=BCnink 2013-01-22 09:= 39:04 UTC --- I think the second C-c should raise a KeyboardInterrupt. At least as long a= s I don't change how SIGINTs are handled. At the moment it depends on which statement your python script is executing when you hit C-c. You cannot have a single try block and catch C-c. Instead= you need a try block and similar code in the stop_handler. I assume a user always expects the same behaviour. Thus, I think it is not optimal that I have to handle C-c at 2 different locations. --=20 Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=3Demail ------- You are receiving this mail because: ------- You are on the CC list for the bug.