From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-22519-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 30879 invoked by alias); 12 Sep 2005 14:30:06 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 30817 invoked by uid 22791); 12 Sep 2005 14:29:58 -0000
Received: from c-24-61-23-223.hsd1.ma.comcast.net (HELO cgf.cx) (24.61.23.223)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 12 Sep 2005 14:29:58 +0000
Received: by cgf.cx (Postfix, from userid 201)
	id 98BEE7A80B2; Mon, 12 Sep 2005 14:29:57 +0000 (UTC)
Date: Mon, 12 Sep 2005 14:30:00 -0000
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: gdb@sources.redhat.com, Himanshu Chandola <himanshuc@picorp.com>
Subject: Re: SIGINT not passed to process on cygwin
Message-ID: <20050912142957.GB10960@trixie.casa.cgf.cx>
Mail-Followup-To: gdb@sources.redhat.com,
	Himanshu Chandola <himanshuc@picorp.com>
References: <43251B11.2030603@picorp.com> <17189.11405.951424.968636@farnswood.snap.net.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <17189.11405.951424.968636@farnswood.snap.net.nz>
User-Agent: Mutt/1.5.8i
X-SW-Source: 2005-09/txt/msg00074.txt.bz2

On Mon, Sep 12, 2005 at 07:21:49PM +1200, Nick Roberts wrote:
>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

Right.  That's what I do when I want the signal to be propagate.

I don't know if this is what is happening but, unfortunately, gdb only
understands windows signals.  Physically pressing CTRL-C is an event
which gdb will recognize as a "SIGINT".  Sending the process a SIGINT
via "kill" or some other method will not be recognized by gdb.

cgf