From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6592 invoked by alias); 12 Sep 2005 07:21:43 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6526 invoked by uid 22791); 12 Sep 2005 07:21:30 -0000 Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 12 Sep 2005 07:21:30 +0000 Received: from farnswood.snap.net.nz (p210-tnt1.snap.net.nz [202.124.110.210]) by viper.snap.net.nz (Postfix) with ESMTP id 0590A67DEF7; Mon, 12 Sep 2005 19:21:27 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id A6DDB62A99; Mon, 12 Sep 2005 08:21:50 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17189.11405.951424.968636@farnswood.snap.net.nz> Date: Mon, 12 Sep 2005 07:21:00 -0000 To: Himanshu Chandola Cc: gdb@sources.redhat.com Subject: SIGINT not passed to process on cygwin In-Reply-To: <43251B11.2030603@picorp.com> References: <43251B11.2030603@picorp.com> X-SW-Source: 2005-09/txt/msg00069.txt.bz2 Himanshu Chandola writes: > Has anyone encountered the following: > attach gdb on cygwin to a running process. Send SIGINT to the process. > gdb handles SIGINT and stops. Try to continue the running process , the > SIGINT is not passed to the process. By default, GDB doesn't pass SIGINT to the process: (gdb) info signal 2 Signal Stop Print Pass to program Description SIGINT Yes Yes No Interrupt If you want it to do so, type: (gdb) handle 2 pass > Worse Ctrl + C interrupts don't > work on the running gdb. > gdb version :6.3.50_2004-12-28-cvs (cygwin-special) Assuming Cygwin has stty, if you type "stty -a" what is SIGINT (intr) bound to? Does it say ^C does anything? If you want it to send SIGINT type: stty intr ^C (remember to use quoted-insert (^V) before typing ^C). Nick