From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15325 invoked by alias); 26 Apr 2010 13:37:07 -0000 Received: (qmail 15303 invoked by uid 22791); 26 Apr 2010 13:37:06 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Apr 2010 13:37:02 +0000 Received: (qmail 7992 invoked from network); 26 Apr 2010 13:37:00 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 26 Apr 2010 13:37:00 -0000 From: Pedro Alves To: John Cortell Subject: Re: sending CTRL-C to Cygwin gdb 6.8 has no effect Date: Mon, 26 Apr 2010 13:37:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-20-generic; KDE/4.3.2; x86_64; ; ) Cc: Dave Korn , gdb@sourceware.org, Joel Brobecker References: <201004231941.o3NJfbWR021914@az33smr01.freescale.net> <201004252225.08587.pedro@codesourcery.com> <201004261330.o3QDUfph028936@az33smr01.freescale.net> In-Reply-To: <201004261330.o3QDUfph028936@az33smr01.freescale.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201004261436.58541.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00141.txt.bz2 On Monday 26 April 2010 14:21:47, John Cortell wrote: > I'm extremely happy to report that avoiding the 'kill' and going with GenerateConsoleCtrlEvent(CTRL_C_EVENT) works. No tweaking via the 'set' commands is even needed. So, it looks like our problems are over. Great. I think we may still have problems with "run" and GUI apps (IMAGE_SUBSYSTEM_WINDOWS_GUI subsystem) that don't have a console at all. I haven't tried this in a while, but I think a console ctrl-c event won't make it to the inferior, and GDB doesn't know to resort automatically to some other means, like DebugBreakProcess. Attaching or setting "set new-console on" should help in this case. I'd be happy to be proven wrong, though. :-) -- Pedro Alves