Re: [PATCH] perl: redirect stderr to /dev/null instead of closing

Thomas Rast wrote: > Closing stderr is a bad idea anyway: there is a very real chance that > we print fatal error messages to some other file that just happens to > be opened on the now-free FD 2. So let's not do that. 100% agreed. FD 0, 1, and 2 should not be closed, way too much potential for

[PATCH] perl: redirect stderr to /dev/null instead of closing

On my system, t9100.1 triggers the following warning: ==352== Syscall param write(buf) points to uninitialised byte(s) ==352==at 0x57119C0: __write_nocancel (in /lib64/libc-2.17.so) ==352==by 0x56AC1D2: _IO_file_write@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==352==by 0x56AC0B1: n