Date: Wed, 28 Feb 2007 15:43:26 -0800
From: Christopher Layne <clayne@anodized.com>
To: cygwin@cygwin.com
Subject: Re: GDB Ctrl-C Interrupt Fails WORKAROUND
Message-ID: <20070228234326.GD9444@ns1.anodized.com>
References: <E5AED0BA-EE62-4D97-96CE-8A96D0C0F559@qualcomm.com> <37FD7E0C-3F61-4EB2-B5A2-9C86C87A45DA@qualcomm.com> <20060615150456.GA7830@trixie.casa.cgf.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060615150456.GA7830@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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/