This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Sensitive/critical bug found?
- From: Andreas Eibach <ae_cygwin at web dot de>
- To: cygwin at cygwin dot com
- Date: Fri, 17 Jun 2005 23:32:31 +0200
- Subject: Sensitive/critical bug found?
It looks that I have.
First of all, ALL version numbers of the tools I used:
GNU find version 4.2.11 (cvs)
GNU xargs version 4.2.11 (cvs)
glib version 2.6.5 (the bug might also appear with other packages)
Assumed I am in ~/devel.
In devel, I do a
tar jxvf glib-2.6.5.tar.bz2
and end up with a glib-2.6.5/ subdirectory. (The problems building glib are NOT supposed to be discussed in this thread)
Now let's look for a specific string:
$ find glib-2.6.5 -name '*' | xargs grep -i 'threads_got_initialized' > out1.log
Works! out1.log is a few kBytes big, and shows the matches I wanted.
Now let's do it a little differently:
$ cd glib-2.6.5
$ find . -name '*' | xargs grep -i 'threads_got_initialized' > out2.log
ATTENTION. out2.log will grow and grow ... and grew more than 2 GB here, until I got a "No space left on device".
$ find . -name '*' | xargs grep -i 'threads_got_initialized' | tee out2.log
works, though.
Can anyone of you reproduce this behavior?
-Andreas
_________________________________________________________________________
Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle
Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179
--
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/