From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22654 invoked by alias); 24 Apr 2010 01:10:06 -0000 Received: (qmail 22643 invoked by uid 22791); 24 Apr 2010 01:10:04 -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; Sat, 24 Apr 2010 01:09:59 +0000 Received: (qmail 29027 invoked from network); 24 Apr 2010 01:09:58 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 24 Apr 2010 01:09:58 -0000 From: Pedro Alves To: gdb@sourceware.org Subject: Re: sending CTRL-C to Cygwin gdb 6.8 has no effect Date: Sat, 24 Apr 2010 01:10:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-20-generic; KDE/4.3.2; x86_64; ; ) Cc: John Cortell , Joel Brobecker References: <201004231941.o3NJfbWR021914@az33smr01.freescale.net> <20100423201109.GQ13204@adacore.com> <201004232035.o3NKZA8B006004@az33smr01.freescale.net> In-Reply-To: <201004232035.o3NKZA8B006004@az33smr01.freescale.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201004240209.55478.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/msg00118.txt.bz2 On Friday 23 April 2010 21:25:10, John Cortell wrote: > cmdline? I.e., if the user hitting CTRL-C in a Windows shell gdb > session successfully interrupts the target program, why is sending > the CTRL-C programatically not working? Any thoughts there? In the latter case, is GDB sharing a console with the inferior? If not sharing a console (native debugging, that is), newer GDB's that postdate that patch Joel pointed you at, will catch the CTRL_C_EVENT themselves, and still try to interrupt the inferior with DebugBreakProcess. Older GDB's, like 6.8, do nothing. With remote debugging, I think sending a ctrl-c to GDB should work, even in 6.8 (provided there's a console and GDB does get the CTRL_C_EVENT, or if this is a cygwin gdb, you sent it a real SIGINT signal). Did you try it? -- Pedro Alves