warning: perl bug in 5.6.x, Win32 (use warnings and STDERR)

yesterday dree stumbled upon what seems a really nasty bug in perl 5.6.x on Win32, so I'm posting this hoping that it can avoid some headache to someone in the (near) future.

note that this seems to have been fixed in perl 5.8.0, so read this only if you have not upgraded (yet)!

the bug appears when you use warnings and close STDERR (which is not a meaningful thing to do, but nonetheless...) and it causes the readline operator (eg. <STDIN>) to only read the first line of a file.

AFFECTED PLATFORMS

first of all, these are the test reports I could gather so far:

OS Perl build Buggy

Windows 2000 Pro, XP Pro v5.6.0 built for MSWin32-x86-multi-thread YES

Windows 2000 Pro, XP Pro v5.6.1 built for MSWin32-x86-multi-thread YES

Windows 2000 Pro, XP Pro v5.6.1 built for cygwin-multi NO

Windows 2000 Pro v5.8.0 built for MSWin32-x86-multi-thread NO

Red Hat Linux release 7.0 (Guinness) v5.6.0 built for i386-linux NO

Red Hat Linux release 7.0 (Guinness) v5.8.0 built for i586-linux-thread-multi-ld NO

summing this up, the bug seems to show only on Win32 with Perl 5.6.0 and 5.6.1 (but not with Cygwin).

DESCRIPTION

this is the exploitation script (I called it dree.pl):

use warnings;
close(STDERR);
open(ME, "$0");
while (<ME>) {
    print;
}
close ME;
[download]

if you run it as it is, it will read (and thus print) only the first line of the file.

if you comment either the first line (use warnings) or the second line (close(STDERR)), the whole file is printed fine.

SUMMARY

if you mysteriously fail to read more than one line from a file, make sure that the following two conditions aren't both met:

use warnings
STDERR is closed

cheers,
Aldo

King of Laziness, Wizard of Impatience, Lord of Hubris

Comment on warning: perl bug in 5.6.x, Win32 (use warnings and STDERR) Download Code

Replies are listed 'Best First'.

Re: warning: perl bug in 5.6.x, Win32 (use warnings and STDERR)
by crazyinsomniac (Prior) on Mar 21, 2003 at 11:28 UTC



open(ME, "$0") or die "crap $!";

close(STDERR);
use warnings;


while (<ME>) {
    print;
}
close ME;
[download]

close(STDERR);

use warnings;

open

This definetly warrants a look-see by the perl 5 porters (p5p).

______crazyinsomniac_____________________________
Of all the things I've lost, I miss my mind the most.
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

[reply]
[d/l]

Re: Re: warning: perl bug in 5.6.x, Win32 (use warnings and STDERR)

by Jenda (Abbot) on Mar 21, 2003 at 13:42 UTC

I tried to play with this a little more. It only prints the first line even if you remove the use warnings and run the script with perl -w or if you set the $^W.

close(STDERR);
open(ME, "$0");
$^W=1;
while (<ME>) {
    print;
}
close ME;
[download]

It fails even if you put the $^W=1; inside the loop, but you always have to close the STDERR before opening the file.

Jenda
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
-- Rick Osborne

[reply]
[d/l]
[select]

Re: warning: perl bug in 5.6.x, Win32 (use warnings and STDERR)
by Mr. Muskrat (Canon) on Mar 21, 2003 at 17:33 UTC

Windows 98 (FE) with AS v5.6.1 build 633 built for MSWin32-x86-multi-thread is also affected.

[reply]