cygwin or gdb question

Bob Rossi
Wed Apr 4 00:35:00 GMT 2007

On Tue, Apr 03, 2007 at 12:54:57PM -0400, Igor Peshansky wrote:
> On Tue, 3 Apr 2007, Bob Rossi wrote:
> > I have one more cgdb issue that seems to be cygwin related. However, it
> > could be a gdb issue. I'm not sure.
> >
> > In verison cgdb-0.6.3 I start GDB up on a pipe and communicate with it
> > over the pipe. This works fine, except that GDB behaves slightly
> > differently when it is invoked on a pipe rather than a pty. That is,
> > GDB provides interactive questions to the user when it's on a pty
> > and not when it's on a pipe.
> >
> > In svn trunk for CGDB I began starting GDB on a pty and communicating
> > with it that way. This fixed a bug for a user on max os X and provided
> > the user with a GDB that acted more like it was on an actual terminal.
> >
> > This seems to work fine on linux, however I noticed a difference on
> > Cygwin. I compile a large GUI application and debug it. I set
> > no breakpoints and type 'r', do some stuff and the GUI and then stop.
> > The debugger is hanging, waiting for something interesting to happen.
> > If I type ctrl-c on linux, it interupts the debugger so that I can
> > set a breakpoint or do something else interesting. If I do this on
> > cygwin, it doesn't interupt the program.
> >
> > In fact, this isn't just a problem with CGDB, the exact same results
> > happen with gdb. So, is it a cygwin or gdb issue that it appears that
> > you can interupt the inferior when gdb is on a pipe, but not when it's
> > on a terminal.
> >
> > Is there an easy way for me to test starting gdb on a pipe outside of
> > CGDB? I would like to reproduce that gdb does interupt the inferior when
> > ctrl-c is typed and GDB is started on a pipe.
> Yes.  Use CYGWIN=tty or rxvt.

Thanks, neither of these showed me the results that I used to get with
cgdb-0.6.3. I've actually decided that I like cgdb working exactly the
same way gdb does. So not being able to interupt the program with ctrl-c
is fine.

Bob Rossi

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list