X-Spam-Check-By:	sourceware.org
Date:	Wed, 28 Feb 2007 15:43:26 -0800
From:	Christopher Layne <clayne AT anodized DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: GDB Ctrl-C Interrupt Fails WORKAROUND
Message-ID:	<20070228234326.GD9444@ns1.anodized.com>
References:	<E5AED0BA-EE62-4D97-96CE-8A96D0C0F559 AT qualcomm DOT com> <37FD7E0C-3F61-4EB2-B5A2-9C86C87A45DA AT qualcomm DOT com> <20060615150456 DOT GA7830 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
In-Reply-To:	<20060615150456.GA7830@trixie.casa.cgf.cx>
User-Agent:	Mutt/1.5.11
X-Assp-Spam-Prob:	0.00000
X-Assp-Whitelisted:	Yes
X-Assp-Envelope-From:	clayne AT ns1 DOT anodized DOT com
X-Assp-Intended-For:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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 Thu, Jun 15, 2006 at 11:04:56AM -0400, Christopher Faylor wrote:
> >I'm happy for you that CTRL-C works for you.  It does not work for me.
> >
> >I'm almost never running gdb from a genuine DOS command prompt.   
> >Sometimes via ssh, sometimes via a terminal emulator.  CTRL-C doesn't  
> >work in those.
> >
> >Also, if you have "tty" in your CYGWIN variable it doesn't work even  
> >from a DOS command prompt.
> 
> Which is exactly what I theorized above.  So, characterizing CTRL-C as
> not working in gdb is rather an overstatement without more details.
> 
> Now you know that you can use a standard console window for debugging
> and all will be well.
> 
> >Lacking the ability to interrupt a running program severely limits  
> >gdb's usefulness.  Fortunately there's a workaround available.
> 
> Yep.  Use a console window.
> 
> cgf

Where in the cygwin source tree would the best place be to look for
where SIGINT handling is being done at the tty/pty level so that I can
remove this pointless limitation from my builds?

-cl

--
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 -