X-Spam-Check-By: sourceware.org Date: Thu, 15 Jun 2006 13:57:14 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: GDB Ctrl-C Interrupt Fails WORKAROUND Message-ID: <20060615175714.GA13956@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.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@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, Jun 15, 2006 at 10:38:57AM -0700, 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. On Cygwin, gdb is the debugger for programs produced by gcc. You are not going to be able to read many (any?) symbols for programs produced by other compilers so there really isn't much of a reason to use gdb to debug non-gcc-produced programs. It is also possible that CTRL-C will not interrupt programs which are compiled for -mwin32. I haven't tried that for a while. That may be what you're seeing when you use the Microsoft Visual C compiler. In any event, at least we're getting details now beyond the "CTRL-C doesn't work with gdb". 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/