Re: some notes on debugging screen

2004-01-21 Thread Igor Pechtchanski
On Wed, 21 Jan 2004, Frédéric L. W. Meunier wrote: > On Wed, 21 Jan 2004, Christopher Faylor wrote: > > > On reflection, the code above (which I happened to have written) didn't > > look right to me, so I did a little digging. I think I was either > > confused when I wrote it or I'm confused now.

Re: some notes on debugging screen

2004-01-21 Thread Frédéric L. W. Meunier
On Wed, 21 Jan 2004, Christopher Faylor wrote: > On reflection, the code above (which I happened to have written) didn't > look right to me, so I did a little digging. I think I was either > confused when I wrote it or I'm confused now. Assuming, as always, that > I'm less confused now than I wa

Re: some notes on debugging screen

2004-01-20 Thread Christopher Faylor
On Tue, Jan 20, 2004 at 09:59:21AM -0800, Rafael Kitover wrote: >FWIF, the code sending the EINVAL is around line 1105 in >winsup/cygwin/fhandler_tty.cc: > >case TIOCSWINSZ: > if (get_ttyp ()->winsize.ws_row != ((struct winsize *) arg)->ws_row > || get_ttyp ()->winsize.ws_col != (

Re: some notes on debugging screen (long) (was: cygwin-1.5.6-1 Vim now broken)

2004-01-20 Thread Christopher Faylor
On Tue, Jan 20, 2004 at 09:59:21AM -0800, Rafael Kitover wrote: >You will not be able to use gdb on a screen binary directly, as you >will get a "must be connected to terminal" error, use something like: This isn't necessary. You should be able to: c:\>set CYGWIN=notty c:\>gdb screen.exe (gdb) s