Bug 98274 - pattern [^\s] fails on string read from plain ascii file
Summary: pattern [^\s] fails on string read from plain ascii file
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: perl (Show other bugs)
(Show other bugs)
Version: 9
Hardware: i686 Linux
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-06-30 09:20 UTC by gordon clare
Modified: 2007-04-18 16:55 UTC (History)
1 user (show)

Fixed In Version: ALL
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-12 00:46:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description gordon clare 2003-06-30 09:20:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016

Description of problem:
I've attached a script -- matching [^\s] works on a string literal containing
simple ascii (no code, no accented chars).  That same string, after being
written and read from a file, prints OK, but the [^\s] match fails.  If the
match is changed to [\S] or \S, the match works on the string read from the
file.  The script works OK if LC_ALL=POSIX is put in the environment or if
binmode is used on the file for input.  I've compiled a new perl in the
meantime, using all default options, and the problem goes away.  But on the perl
that comes with the redhat distribution the problem is there.

The script:

my $x = "this\n";

open(F, ">/tmp/test.txt");
print F "$x";

open(F, "</tmp/test.txt");
my @lines = <F>;

if ($x =~ /^\s*([^\s]+)/)
    print "'$x' internal string matched OK\n";
    print "'$x' internal string FAILED!\n";

for $x (@lines)
    if ($x =~ /^\s*([^\s]+)/)
        print "'$x' file string matched OK\n";
        print "'$x' file string FAILED!\n";

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.install redhat 9
2.run the above script

Actual Results:  'this
' internal string matched OK
' file string FAILED!

Expected Results:  'this
' internal string matched OK
' file string matched OK

Additional info:

*any* of the following make the script work:
  - LC_ALL=POSIX in the environment.
  - use binmode(F) on the input file.
  - change [^\s] to [\S] or \S.

Comment 1 Jan "Yenya" Kasprzak 2003-07-11 17:40:17 UTC
This bug also causes the muttprint (http://muttprint.sourceforge.net/) failure
on RH9. According to the muttprint home page the Perl in rawhide works OK
(I have not verified this though).

Comment 2 Need Real Name 2003-07-18 16:55:51 UTC
This error causes CGI.pm to fail in offline debugging mode, since 
the module reads from STDIN in that case.  When used in this fashion, the 
program hangs when the input data is passed from CGI.pm to shellword.pl for 
parsing (where the pattern [^\s\\'"] is used), making it appear to the user 
as though ^D fails to end keyboard input.

The problem seems to affect all character classes with negated escape 
sequences, not just [^\s], as can be seen in the following:
$_ = "somestring";
open OUTF, ">testdata.$$" or die;
print OUTF $_;
close OUTF;
open INF, "<testdata.$$" or die;

# uncomment the next line to recreate the problem
# $_ = <INF>;

close INF;
/[^\d]+/ ? print "pattern succeeded\n" : print "pattern failed\n";

The fix "export LC_ALL=POSIX" mentioned above works to correct this problem in
all the cases I've tested.

Comment 3 Bishop Clark 2003-08-11 18:20:15 UTC
I know this thing's languished a MONTH with no change/comment, but in case it's
still a problem for you, rumour has it that the RawHide release of perl has a
mod that fixes this anomaly-not-bug .

Give it a try and maybe let Chip cross this thing off his massive to-do list? 
I'll be trying it in a bit, for about 4 similar problems I'm having with the
perl 580-88 on RHL9 - it's like this perl Unicode thing's causing almost as much
grief and pain as the Kerberos-devel feature-not-bug.

Comment 4 Bert de Bruijn 2004-04-06 08:33:07 UTC
This bug was apparently fixed in perl-5.8.0-88.3 (rh9-updates, build
date 2003-08-13). Can someone close it please ?

Comment 5 Jason Vas Dias 2005-11-12 00:46:10 UTC
This bug is fixed in all current Red Hat perl releases - closing.

Note You need to log in before you can comment on or make changes to this bug.