X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: GDB Ctrl-C Interrupt Fails WORKAROUND Date: Thu, 15 Jun 2006 20:07:46 +0100 Message-ID: <005f01c690ae$fc8fce70$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: 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 15 June 2006 18:39, Kyle McKay wrote: > On 15 Jun 2006 11:04:56 -0400, Christopher Faylor wrote: >>> Lacking the ability to interrupt a running program severely limits >>> gdb's usefulness. Fortunately there's a workaround available. >> >> Yep. Use a console window. > > Maybe I haven't been clear. THIS DOES NOT WORK. > > Compile the below hellowin.c program with the m$ visual C compiler. > Start it up using gdb. Run it, press CTRL-C, NOTHING HAPPENS. OTOH, Ctrl-Break 'works', but is not intercepted by GDB, which just reports "Program exited normally". cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/