On Fri, Mar 17, 2006 at 10:15:13AM -0500, Christopher Faylor wrote: > 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.
O, right. Sorry. The bug I was talking about only appears when you fork/exec GDB from within a program. Bob Rossi -- 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/