On Sun, Sep 09, 2007 at 10:08:14PM +0200, Andreas Schwab wrote: > Stephane Chazelas <[EMAIL PROTECTED]> writes: > > > On Sun, Sep 09, 2007 at 07:10:59PM +0100, Stephane Chazelas wrote: > > [...] > >> What OS and version of glibc? I do get the error message but I > >> get both a and b in the file. > >> > >> That was on Linux, glibc 2.6.1. > > [...] > > > > Actually, > > > > bash -c 'echo a; echo b > a' >&- > > > > is enough for me to reproduce the problem. > > Guess you have a buggy libc, then. [...]
I wouldn't be surprised if it has to do with the fix to debian bug #429021. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429021 (I'm CCing Dmitry who is the author of that change according to bugs.debian.org) I was testing with debian package 2.6.1-2 that includes Dmitry's fix for that bug. I don't know if that fix will is planned to be included in the GNU tree, it doesn't seem it yet in the glibc CVS repository. Now, I'm not sure if we can say that the new glibc behavior observed is bogus (other than it's different from the behavior observed in all the libcs I tried with). It is not a harmless change, for sure as it seems to have broken at least bash, zsh and possibly ksh93. Dmitry, you may find that whole thread at: http://groups.google.com/group/gnu.bash.bug/browse_thread/thread/e311bdd4f945a21e/621b7189217760f1 Best regards, Stéphane
