1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

[russell christian sears]

I have found a problem using less and grep to search a file.  The file is
available at: http://www.cis.ohio-state.edu/~sears/file.txt (It is over 1
megabyte, so I did not include it in this message.)

I am using bash, and a complete, current installation of cygwin.

When I run the command `less file.txt | grep cygwin` it sometimes fails to
find a match in the file, even though the file does contain the string.

It seems to be sporadic, but I have been able to reproduce the problem on
three machines, each of which ran at about 700mhz.  Other commands that
seem to work as expected follow:

less file.txt | cat | grep cygwin
cat file.txt | grep cygwin
grep cygwin file.txt

If you have difficulty reproducing the bug, try running the command
multiple times (eg: by repeating <up-arrow>, <enter> rapidly).  Some
installations will only rarely have a problem, others will rarely yield
the correct result.  On systems that usually produce the correct result,
re-running the command rapidly seems to increase the likelihood of the
problem
ocurring.

Also, the string "cygwin" always appears at the end of a line in the file,
which may be related to this bug.

I have tried both version 1.1.8 and the current cygwin distribution.
(1.3.2)  Both seem to suffer from this problem.

As a control, I've checked this against a Linux system, and the bug did
not exist there.

Below, the mount mode is listed as textmode.  The bug exists under binmode
as well.

Here is the output of cygcheck -s -v -r > cygcheck.out:

Cygnus Win95/NT Configuration Diagnostics
Current System Time: Thu Jun 28 15:48:34 2001

WinNT Ver 5.0 build 2195

Path:   /usr/local/bin
        /usr/bin
        /bin
        /cygdrive/c/Perl/bin/
        /cygdrive/c/WINNT/system32
        /cygdrive/c/WINNT
        /cygdrive/c/WINNT/System32/Wbem

SysDir: C:\WINNT\System32
WinDir: C:\WINNT

PWD = `/home/Administrator'
USER = `Administrator'
MAKE_MODE = `unix'
HOME = `/home/Administrator'

NUMBER_OF_PROCESSORS = `1'
PROMPT = `$P$G'
LOGONSERVER = `\\SERVER-2'
OS2LIBPATH = `C:\WINNT\system32\os2\dll;'
COMSPEC = `C:\WINNT\system32\cmd.exe'
!C: = `C:\cygwin\bin'
SYSTEMDRIVE = `C:'
HOSTNAME = `RSEARS'
PROCESSOR_REVISION = `0803'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
COMPUTERNAME = `RSEARS'
WINDIR = `C:\WINNT'
USERPROFILE = `C:\Documents and Settings\rsears'
PS1 = `\[\033]0;\w\007
\033[32m\]\u@\h \[\033[33m\w\033[0m\]
$ '
HOMESHARE = `\\file1\users\rsears'
PROGRAMFILES = `C:\Program Files'
USERDNSDOMAIN = `colmol.com'
MACHTYPE = `i686-pc-cygwin'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 3, GenuineIntel'
OS = `Windows_NT'
OLDPWD = `/usr/bin'
PROCESSOR_ARCHITECTURE = `x86'
TEMP = `/cygdrive/c/DOCUME~1/rsears/LOCALS~1/Temp'
PROCESSOR_LEVEL = `6'
SYSTEMROOT = `C:\WINNT'
HOMEDRIVE = `M:'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
SHLVL = `1'
APPDATA = `C:\Documents and Settings\rsears\Application Data'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
HOMEPATH = `\'
USERDOMAIN = `CMS'
USERNAME = `rsears'
SHELL = `/bin/bash'
HOSTTYPE = `i686'
OSTYPE = `cygwin'
TERM = `cygwin'
_ = `/usr/bin/cygcheck'
TZ = `EST5EDT4,M4.1.0/2,M10.5.0/2'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
  (default) = `/cygdrive'
  cygdrive flags = 0x00000020
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\S
tart Menu\Programs\Cygnus Solutions
  (default) = (unsupported type)
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
  (default) = `C:\cygwin'
  flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
  (default) = `C:/cygwin/bin'
  flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
  (default) = `C:/cygwin/lib'
  flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options

a:  fd           N/A    N/A
c:  hd  NTFS   28615Mb  19% CP CS UN PA FC
d:  cd           N/A    N/A
m:  net NTFS   131798Mb  26% CP CS UN PA FC     Data Disk

C:\cygwin\bin  /usr/bin  system  textmode
C:\cygwin\lib  /usr/lib  system  textmode
C:\cygwin  /        system  textmode
c:    /cygdrive/c  user    textmode,noumount
m:    /cygdrive/m  user    textmode,noumount

Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cpp.exe
Found: C:\cygwin\bin\find.exe
Found: C:\cygwin\bin\gcc.exe
Found: C:\cygwin\bin\gdb.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\sh.exe

   56k 2000/12/03 C:\cygwin\bin\cygbz21.0.dll - os=4.0 img=1.0 sys=4.0
                  "cygbz21.0.dll" v0.0 ts=2000/11/20 18:53
   45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
                  "cygform5.dll" v0.0 ts=2001/4/25 1:28
   18k 2000/10/23 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm.dll" v0.0 ts=2000/10/22 22:26
   17k 2001/01/07 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
                  "cyghistory4.dll" v0.0 ts=2001/1/6 23:34
   14k 2000/10/23 C:\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl.dll" v0.0 ts=2000/10/23 15:02
   81k 2000/12/05 C:\cygwin\bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0
                  "cygitcl30.dll" v0.0 ts=2000/11/25 20:43
   35k 2000/12/05 C:\cygwin\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0
                  "cygitk30.dll" v0.0 ts=2000/11/25 20:43
   45k 2000/10/22 C:\cygwin\bin\cygjbig1.dll - os=4.0 img=1.0 sys=4.0
                  "cygjbig1.dll" v0.0 ts=2000/10/22 19:06
  119k 2001/06/06 C:\cygwin\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0
                  "cygjpeg6b.dll" v0.0 ts=2001/6/6 0:27
   26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu5.dll" v0.0 ts=2001/4/25 1:27
  156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses++5.dll" v0.0 ts=2001/4/25 1:29
  226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses5.dll" v0.0 ts=2001/4/25 1:17
   15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel5.dll" v0.0 ts=2001/4/25 1:27
  163k 2001/05/06 C:\cygwin\bin\cygpng2.dll - os=4.0 img=1.0 sys=4.0
                  "cygpng2.dll" v0.0 ts=2001/5/6 0:05
  108k 2001/01/07 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
                  "cygreadline4.dll" v0.0 ts=2001/1/6 23:34
  390k 2000/12/05 C:\cygwin\bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtcl80.dll" v0.0 ts=2000/11/25 20:39
    5k 2000/12/05 C:\cygwin\bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0
   10k 2000/12/05 C:\cygwin\bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtclreg80.dll" v0.0 ts=2000/11/25 20:39
  245k 2001/06/12 C:\cygwin\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0
                  "cygtiff3.dll" v0.0 ts=2001/6/12 13:25
  623k 2000/12/05 C:\cygwin\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtk80.dll" v0.0 ts=2000/11/25 20:43
   41k 2001/05/28 C:\cygwin\bin\cygXpm-noX4.dll - os=4.0 img=1.0 sys=4.0
                  "cygXpm-noX4.dll" v0.0 ts=2001/5/28 13:57
   49k 2001/02/03 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
                  "cygz.dll" v0.0 ts=2001/2/3 15:35
  678k 2001/05/21 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2001/5/20 23:28
    Cygwin DLL version info:
        dll major: 1003
        dll minor: 2
        dll epoch: 19
        dll bad signal mask: 19005
        dll old termios: 5
        dll malloc env: 28
        api major: 0
        api minor: 39
        shared data: 3
        dll identifier: cygwin1
        mount registry: 2
        cygnus registry name: Cygnus Solutions
        cygwin registry name: Cygwin
        program options name: Program Options
        cygwin mount registry name: mounts v2
        cygdrive flags: cygdrive flags
        cygdrive prefix: cygdrive prefix
        cygdrive default prefix:
        build date: Sun May 20 23:28:17 EDT 2001
        shared id: cygwin1S3

Use -h to see help about each section





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

[Randall R Schulz]

Russell,

Depending on the terminal you're using, which termcap / terminfo entry 
you've specified and the terminal window's size, less will produce 
different literal output sequences as it paginates and line-wraps its 
input. (Although I would have thought that if the output was not a tty, it 
would forgo such manipulations and act just like cat.)

You really shouldn't use a program explicitly designed for visual display 
on a terminal to feed a pipe to grep or any other processor.

Just grep the target file.

Randall Schulz
Mountain View, CA USA


At 06:21 2001-07-02, russell christian sears wrote:
>I have found a problem using less and grep to search a file.  The file is 
>available at: http://www.cis.ohio-state.edu/~sears/file.txt (It is over 1 
>megabyte, so I did not include it in this message.)
>
>I am using bash, and a complete, current installation of cygwin.
>
>When I run the command `less file.txt | grep cygwin` it sometimes fails to 
>find a match in the file, even though the file does contain the string.
>
>It seems to be sporadic, but I have been able to reproduce the problem on 
>three machines, each of which ran at about 700mhz.  Other commands that 
>seem to work as expected follow:
>
>less file.txt | cat | grep cygwin
>cat file.txt | grep cygwin
>grep cygwin file.txt
>
>If you have difficulty reproducing the bug, try running the command 
>multiple times (eg: by repeating <up-arrow>, <enter> rapidly).  Some 
>installations will only rarely have a problem, others will rarely yield 
>the correct result.  On systems that usually produce the correct result, 
>re-running the command rapidly seems to increase the likelihood of the 
>problem ocurring.
>
>Also, the string "cygwin" always appears at the end of a line in the file, 
>which may be related to this bug.
>
>I have tried both version 1.1.8 and the current cygwin distribution. 
>(1.3.2)  Both seem to suffer from this problem.
>
>As a control, I've checked this against a Linux system, and the bug did 
>not exist there.
>
>Below, the mount mode is listed as textmode.  The bug exists under binmode 
>as well.
>
>...


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

[Randall R Schulz]

Russell,

I should have tested my hypothesis before sending. Apparently it is not 
correct. When its output is directed into a pipe, less does indeed forgo 
altering the input data.

All my mounts are binmode. Perhaps there's something going on with that?

Randall


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

[russell christian sears]

On Mon, 2 Jul 2001, Randall R Schulz wrote:

> Russell,
>
> I should have tested my hypothesis before sending. Apparently it is not
> correct. When its output is directed into a pipe, less does indeed forgo
> altering the input data.
>
> All my mounts are binmode. Perhaps there's something going on with that?
>
> Randall
>

Our resident long-term cygwin user suggested that also.  The problem
originally surfaced with all mounts set to binmode, we later switched some
into textmode, but the problem persisted.

Ron Cook said the problem does not exist under Windows ME on his HP.
Maybe this is specific to windows 2000, or some sort of timing issue.

Unfortunately, the computers I have access to all run at roughly the same
speed, so I can't rule out that as the problem.

-Rusty



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

[russell christian sears]

Maybe it's specific to Windows 2000 or Windows 2000 Professional.  Has
anyone been able / tried to reproduce the problem using 2000?

If so, with what hardware?

(I'm using a Dell Dimension 4100.)

On Mon, 2 Jul 2001, Ronald W. Cook wrote:

> I am also all binmode and at 700 Mhz.
>
> Ron
> ----- Original Message -----
> From: "russell christian sears" <sears@cis.ohio-state.edu>
> To: "Randall R Schulz" <rrschulz@cris.com>
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

[russell christian sears]

Sorry about the long response time.

I'm not trying to use grep as a pager, instead, I'm using it like cat.
(If it sees that it's writing to a pipe instead of a terminal, it behaves
like cat.)  I'm concerned that the cygwin libraries are somehow mangling
the pipe.  I've only been able to reproduce it on systems with an almost
identical configuration to mine, (Dell Dimension 4100, Windows 2000
Professional) but I am worried that it could affect other users, and
result in mangled or incorrect output.

On Tue, 3 Jul 2001, Sheldon, Ken wrote:

> I have a simple question: Why are you running less at the front of the
> pipeline instead of grep?  I would perform the task you describe using:
> grep "cygwin" file.txt | less
> ----Ken
>
>
>
>
>
> -----Original Message-----
> From: russell christian sears [ mailto:sears@cis.ohio-state.edu ]
> Sent: Monday, July 02, 2001 8:21 AM
> To: cygwin@cygwin.com
> Subject: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)
>
>
> I have found a problem using less and grep to search a file.  The file is
> available at: http://www.cis.ohio-state.edu/~sears/file.txt (It is over 1
> megabyte, so I did not include it in this message.)
>
> I am using bash, and a complete, current installation of cygwin.
>
> When I run the command `less file.txt | grep cygwin` it sometimes fails to
> find a match in the file, even though the file does contain the string.
>
> It seems to be sporadic, but I have been able to reproduce the problem on
> three machines, each of which ran at about 700mhz.  Other commands that
> seem to work as expected follow:
>
> less file.txt | cat | grep cygwin
> cat file.txt | grep cygwin
> grep cygwin file.txt
>
> If you have difficulty reproducing the bug, try running the command
> multiple times (eg: by repeating <up-arrow>, <enter> rapidly).  Some
> installations will only rarely have a problem, others will rarely yield
> the correct result.  On systems that usually produce the correct result,
> re-running the command rapidly seems to increase the likelihood of the
> problem
> ocurring.
>
> Also, the string "cygwin" always appears at the end of a line in the file,
> which may be related to this bug.
>
> I have tried both version 1.1.8 and the current cygwin distribution.
> (1.3.2)  Both seem to suffer from this problem.
>
> As a control, I've checked this against a Linux system, and the bug did
> not exist there.
>
> Below, the mount mode is listed as textmode.  The bug exists under binmode
> as well.
>
> Here is the output of cygcheck -s -v -r > cygcheck.out:
>
> Cygnus Win95/NT Configuration Diagnostics
> Current System Time: Thu Jun 28 15:48:34 2001
>
> WinNT Ver 5.0 build 2195
>
> Path:   /usr/local/bin
>         /usr/bin
>         /bin
>         /cygdrive/c/Perl/bin/
>         /cygdrive/c/WINNT/system32
>         /cygdrive/c/WINNT
>         /cygdrive/c/WINNT/System32/Wbem
>
> SysDir: C:\WINNT\System32
> WinDir: C:\WINNT
>
> PWD = `/home/Administrator'
> USER = `Administrator'
> MAKE_MODE = `unix'
> HOME = `/home/Administrator'
>
> NUMBER_OF_PROCESSORS = `1'
> PROMPT = `$P$G'
> LOGONSERVER = `\\SERVER-2'
> OS2LIBPATH = `C:\WINNT\system32\os2\dll;'
> COMSPEC = `C:\WINNT\system32\cmd.exe'
> !C: = `C:\cygwin\bin'
> SYSTEMDRIVE = `C:'
> HOSTNAME = `RSEARS'
> PROCESSOR_REVISION = `0803'
> PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
> COMPUTERNAME = `RSEARS'
> WINDIR = `C:\WINNT'
> USERPROFILE = `C:\Documents and Settings\rsears'
> PS1 = `\[\033]0;\w\007
> \033[32m\]\u@\h \[\033[33m\w\033[0m\]
> $ '
> HOMESHARE = `\\file1\users\rsears'
> PROGRAMFILES = `C:\Program Files'
> USERDNSDOMAIN = `colmol.com'
> MACHTYPE = `i686-pc-cygwin'
> PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 3, GenuineIntel'
> OS = `Windows_NT'
> OLDPWD = `/usr/bin'
> PROCESSOR_ARCHITECTURE = `x86'
> TEMP = `/cygdrive/c/DOCUME~1/rsears/LOCALS~1/Temp'
> PROCESSOR_LEVEL = `6'
> SYSTEMROOT = `C:\WINNT'
> HOMEDRIVE = `M:'
> ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
> SHLVL = `1'
> APPDATA = `C:\Documents and Settings\rsears\Application Data'
> COMMONPROGRAMFILES = `C:\Program Files\Common Files'
> HOMEPATH = `\'
> USERDOMAIN = `CMS'
> USERNAME = `rsears'
> SHELL = `/bin/bash'
> HOSTTYPE = `i686'
> OSTYPE = `cygwin'
> TERM = `cygwin'
> _ = `/usr/bin/cygcheck'
> TZ = `EST5EDT4,M4.1.0/2,M10.5.0/2'
>
> HKEY_CURRENT_USER\Software\Cygnus Solutions
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
>   (default) = `/cygdrive'
>   cygdrive flags = 0x00000020
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
> HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrd
> er\S
> tart Menu\Programs\Cygnus Solutions
>   (default) = (unsupported type)
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
>   (default) = `C:\cygwin'
>   flags = 0x00000008
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
>   (default) = `C:/cygwin/bin'
>   flags = 0x00000008
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
>   (default) = `C:/cygwin/lib'
>   flags = 0x00000008
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
>
> a:  fd           N/A    N/A
> c:  hd  NTFS   28615Mb  19% CP CS UN PA FC
> d:  cd           N/A    N/A
> m:  net NTFS   131798Mb  26% CP CS UN PA FC     Data Disk
>
> C:\cygwin\bin  /usr/bin  system  textmode
> C:\cygwin\lib  /usr/lib  system  textmode
> C:\cygwin  /        system  textmode
> c:    /cygdrive/c  user    textmode,noumount
> m:    /cygdrive/m  user    textmode,noumount
>
> Found: C:\cygwin\bin\bash.exe
> Found: C:\cygwin\bin\cat.exe
> Found: C:\cygwin\bin\cpp.exe
> Found: C:\cygwin\bin\find.exe
> Found: C:\cygwin\bin\gcc.exe
> Found: C:\cygwin\bin\gdb.exe
> Found: C:\cygwin\bin\ld.exe
> Found: C:\cygwin\bin\ls.exe
> Found: C:\cygwin\bin\make.exe
> Found: C:\cygwin\bin\sh.exe
>
>    56k 2000/12/03 C:\cygwin\bin\cygbz21.0.dll - os=4.0 img=1.0 sys=4.0
>                   "cygbz21.0.dll" v0.0 ts=2000/11/20 18:53
>    45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
>                   "cygform5.dll" v0.0 ts=2001/4/25 1:28
>    18k 2000/10/23 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
>                   "cyggdbm.dll" v0.0 ts=2000/10/22 22:26
>    17k 2001/01/07 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
>                   "cyghistory4.dll" v0.0 ts=2001/1/6 23:34
>    14k 2000/10/23 C:\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0
>                   "cygintl.dll" v0.0 ts=2000/10/23 15:02
>    81k 2000/12/05 C:\cygwin\bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0
>                   "cygitcl30.dll" v0.0 ts=2000/11/25 20:43
>    35k 2000/12/05 C:\cygwin\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0
>                   "cygitk30.dll" v0.0 ts=2000/11/25 20:43
>    45k 2000/10/22 C:\cygwin\bin\cygjbig1.dll - os=4.0 img=1.0 sys=4.0
>                   "cygjbig1.dll" v0.0 ts=2000/10/22 19:06
>   119k 2001/06/06 C:\cygwin\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0
>                   "cygjpeg6b.dll" v0.0 ts=2001/6/6 0:27
>    26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
>                   "cygmenu5.dll" v0.0 ts=2001/4/25 1:27
>   156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
>                   "cygncurses++5.dll" v0.0 ts=2001/4/25 1:29
>   226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
>                   "cygncurses5.dll" v0.0 ts=2001/4/25 1:17
>    15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
>                   "cygpanel5.dll" v0.0 ts=2001/4/25 1:27
>   163k 2001/05/06 C:\cygwin\bin\cygpng2.dll - os=4.0 img=1.0 sys=4.0
>                   "cygpng2.dll" v0.0 ts=2001/5/6 0:05
>   108k 2001/01/07 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
>                   "cygreadline4.dll" v0.0 ts=2001/1/6 23:34
>   390k 2000/12/05 C:\cygwin\bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0
>                   "cygtcl80.dll" v0.0 ts=2000/11/25 20:39
>     5k 2000/12/05 C:\cygwin\bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0
>    10k 2000/12/05 C:\cygwin\bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0
>                   "cygtclreg80.dll" v0.0 ts=2000/11/25 20:39
>   245k 2001/06/12 C:\cygwin\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0
>                   "cygtiff3.dll" v0.0 ts=2001/6/12 13:25
>   623k 2000/12/05 C:\cygwin\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0
>                   "cygtk80.dll" v0.0 ts=2000/11/25 20:43
>    41k 2001/05/28 C:\cygwin\bin\cygXpm-noX4.dll - os=4.0 img=1.0 sys=4.0
>                   "cygXpm-noX4.dll" v0.0 ts=2001/5/28 13:57
>    49k 2001/02/03 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
>                   "cygz.dll" v0.0 ts=2001/2/3 15:35
>   678k 2001/05/21 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                   "cygwin1.dll" v0.0 ts=2001/5/20 23:28
>     Cygwin DLL version info:
>         dll major: 1003
>         dll minor: 2
>         dll epoch: 19
>         dll bad signal mask: 19005
>         dll old termios: 5
>         dll malloc env: 28
>         api major: 0
>         api minor: 39
>         shared data: 3
>         dll identifier: cygwin1
>         mount registry: 2
>         cygnus registry name: Cygnus Solutions
>         cygwin registry name: Cygwin
>         program options name: Program Options
>         cygwin mount registry name: mounts v2
>         cygdrive flags: cygdrive flags
>         cygdrive prefix: cygdrive prefix
>         cygdrive default prefix:
>         build date: Sun May 20 23:28:17 EDT 2001
>         shared id: cygwin1S3
>
> Use -h to see help about each section
>
>
>
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)

[Ronald W. Cook]

Russell,

Following your instructions, as well as using grep by itself, I was
not able to detect any malfunctions in ten trials each.  In every
case, two lines with cygwin at the end were proffered.

I am using ME on an hp5195 current cygwin.

Regards,
Ron Cook
cowaro.com


----- Original Message -----
From: "russell christian sears" <sears@cis.ohio-state.edu>
To: <cygwin@cygwin.com>
Sent: Monday, July 02, 2001 9:21 AM
Subject: 1.3.2, 1.1.8: Pipelines losing data? (Windows 2000)


> I have found a problem using less and grep to search a file.  The file is
> available at: http://www.cis.ohio-state.edu/~sears/file.txt (It is over 1
> megabyte, so I did not include it in this message.)
>
> I am using bash, and a complete, current installation of cygwin.
>
> When I run the command `less file.txt | grep cygwin` it sometimes fails to
> find a match in the file, even though the file does contain the string.
>
> It seems to be sporadic, but I have been able to reproduce the problem on
> three machines, each of which ran at about 700mhz.  Other commands that
> seem to work as expected follow:
>
> less file.txt | cat | grep cygwin
> cat file.txt | grep cygwin
> grep cygwin file.txt
>
> If you have difficulty reproducing the bug, try running the command
> multiple times (eg: by repeating <up-arrow>, <enter> rapidly).  Some
> installations will only rarely have a problem, others will rarely yield
> the correct result.  On systems that usually produce the correct result,
> re-running the command rapidly seems to increase the likelihood of the
> problem
> ocurring.
>
> Also, the string "cygwin" always appears at the end of a line in the file,
> which may be related to this bug.
>
> I have tried both version 1.1.8 and the current cygwin distribution.
> (1.3.2)  Both seem to suffer from this problem.
>
> As a control, I've checked this against a Linux system, and the bug did
> not exist there.
>
> Below, the mount mode is listed as textmode.  The bug exists under binmode
> as well.
>
> Here is the output of cygcheck -s -v -r > cygcheck.out:
>
> Cygnus Win95/NT Con


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/