X-Spam-Check-By: sourceware.org Date: Fri, 17 Mar 2006 10:15:13 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: GDB Interrupts on Cygwin Message-ID: <20060317151513.GA22857@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <2284342f0603170055i5268807bn83042ea5988aa46 AT mail DOT gmail DOT com> <20060317115655 DOT GH30980 AT brasko DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060317115655.GH30980@brasko.net> 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 Fri, Mar 17, 2006 at 06:56:55AM -0500, Bob Rossi wrote: >On Fri, Mar 17, 2006 at 03:55:08AM -0500, Doug Bohl wrote: >> When running a Windows application from GDB, GDB gives control to the >> application at a certain point. It would be nice to, at an arbitrary >> time, suspend the application and give control back to GDB. I know >> that I can set breakpoints, but sometimes I don't know exactly when I >> want to break until after I'm running the application. Ctrl-C >> supposedly sends the SIGINT signal to GDB, breaking the running >> application and restoring control to GDB. However, this does not >> appear to work, at least not on Cygwin. > >Even though this may seem strange, try this. Before starting GDB, type >'tty' at the console. Then, after you start GDB, run the command 'tty >outputofttycommandfromconsole'. I think this will enable the ^c. This is a no-voodoo zone. CTRL-C works fine in gdb. I use it ALL of the time. Maybe the OP has CYGWIN=tty set or is trying to run from rxvt. If so, don't do that. Run gdb from a windows console and it should work fine. 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/