Using a different version of perl is a possibility, but I would think that this would be considered an xterm bug (or does every application that cygwin needs to interact with need to be re-written/ported to run inside of cygwin?)
Does anyone have any suggestions about where to look to start to debug the problem (i.e. determine if is an xterm problem or a an ActiveState problem)? --- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Wed, Dec 22, 2004 at 01:51:04PM -0800, Tom Goetze wrote: > >Something very strange I discovered today, however, is that > if I try to use > >the perl debugger like this: > > > >perl -d -e 0 > > > >then the perl debugging prompt does not appear in the xterm > window, but > >instead it appears (with mangled characters) in the cygwin > terminal from > >which I ran "startx". > > > >2. The version of perl is the ActiveState one that I > installed outside of > >cygwin, but that gets picked up from my Windows user's PATH. > > > >In particular, > >$ which perl > >/cygdrive/c/Perl/bin/perl > > > >Anything jump out as a potential problem for me (or a quick > fix)? > > Use cygwin's perl? ActiveState perl obviously doesn't > understand cygwin's > ptys. > > cgf >