X-Spam-Check-By: sourceware.org Date: Thu, 15 Jun 2006 00:44:05 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: GDB Ctrl-C Interrupt Fails WORKAROUND Message-ID: <20060615044405.GA27636@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Wed, Jun 14, 2006 at 08:29:50PM -0700, Kyle McKay wrote: >If you have ever tried to interrupt a program running under cygwin >gdb, you have probably experienced some frustration. Especially if >the program was built with -mno-cygwin. No I never have. In fact I often rely on CTRL-C interrupting the program. It doesn't matter whether the program is built with -mno-cygwin or not. In fact, I am sometimes frustrated when I actually want the CTRL-C to be propagated to the program but then I remember about the "handle" command. The only time that I can think of when a CTRL-C would not interrupt a program would be when you're running gdb under a cygwin pty or tty. But it's usually easy enough not to do that if you are debugging a problem. cgf -- 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/