From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13747 invoked by alias); 11 Jan 2012 20:56:13 -0000 Received: (qmail 13739 invoked by uid 22791); 11 Jan 2012 20:56:13 -0000 X-SWARE-Spam-Status: No, hits=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Jan 2012 20:56:00 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0BKtxhm022841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jan 2012 15:55:59 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q0BKtwCA027974; Wed, 11 Jan 2012 15:55:58 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id q0BKtv0J009138; Wed, 11 Jan 2012 15:55:57 -0500 From: Tom Tromey To: Doug Evans Cc: Khoo Yit Phang , gdb-patches@sourceware.org Subject: Re: Handle SIGINT in Python References: Date: Wed, 11 Jan 2012 20:59:00 -0000 In-Reply-To: (Doug Evans's message of "Tue, 10 Jan 2012 13:46:31 -0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00368.txt.bz2 >>>>> "Doug" == Doug Evans writes: Doug> There is value in having the SIGINT *only* affect the inferior. Doug> It's up to the script to handle the various reasons why the inferior Doug> may have stopped, and you don't (generally) want to interfere with Doug> that (by interrupting the script too). I think Python code should have to request something like this specially. The scripting case is less usual than the interactive debugging (perhaps with some Python helper code) case. I think it would be weird for the behavior the user sees, by default, to depend on whether Python or GDB code was active at the moment of C-c. That is, a C-c when processing a 'python' command in a breakpoint's 'commands' list should have the same general effect as if we were processing any other command. Tom