X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: GDB Interrupts on Cygwin
Date:	Fri, 17 Mar 2006 10:26:56 -0000
Message-ID:	<006c01c649ad$51266b40$a501a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
In-Reply-To:	<2284342f0603170055i5268807bn83042ea5988aa46@mail.gmail.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 17 March 2006 08:55, Doug Bohl wrote:

> When running a Windows application from GDB,

> Ctrl-C
> supposedly sends the SIGINT signal to GDB, breaking the running
> application and restoring control to GDB.  However, this does not
> appear to work, at least not on Cygwin.
> 
> I've tried /bin/kill -f -s SIGINT pid.  Sending SIGINT, or in fact any
> other signal, simply terminates the Windows application.

  It's not entirely surprising that windows applications aren't aware of
cygwin signal handling!

  Have you tried running it with a mingw (i.e. windows native) version of gdb?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -