Skip Menu |
 

This queue is for tickets about the PathTools CPAN distribution.

Report information
The Basics
Id: 65689
Status: open
Priority: 0/
Queue: PathTools

People
Owner: Nobody in particular
Requestors: alexander.haeckel [...] web.de
jkeenan [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: cwd.t fails for pathologically named file.
Date: Sun, 13 Feb 2011 02:41:13 +0100
To: bug-PathTools [...] rt.cpan.org
From: Alexander Haeckel <alexanderhaeckel [...] lavabit.com>
Download (untitled) / with headers
text/plain 873b
Hi, I had a file named "root^J" in my "/" directory where the filename ended with a newline on a AMD64/Debian Lenny box. This strange file turned out to be the "AMD Power Monitor Setting File". Don't remember how I got that thing but it brought me this crash: t/cwd.t ................. 1/34 # Failed test (t/cwd.t at line 247) # got: '/root' # expected: '/root # ' # Failed test (t/cwd.t at line 248) # got: '/root' # expected: '/root # ' # Looks like you failed 2 tests of 34. I resolved the matter by simply renaming the file, but I would recommend to filter out such pathologically named files before calling Cwd::fast_abs_path($file) or Cwd::fast_abs_path($file) at least in t/cwd.t . Kind regards, Alexander Haeckel -- "I can't understand why people are frightened of new ideas. I'm frightened of the old ones.” - John Cage
On Sat Feb 12 20:41:32 2011, alexander.haeckel@web.de wrote: Show quoted text
> Hi, > I had a file named "root^J" in my "/" directory where the filename > ended with a newline on a AMD64/Debian Lenny box. > This strange file turned out to be the > "AMD Power Monitor Setting File". > Don't remember how I got that thing but it brought me this crash: > t/cwd.t ................. 1/34 > # Failed test (t/cwd.t at line 247) > # got: '/root' > # expected: '/root > # ' > > # Failed test (t/cwd.t at line 248) > # got: '/root' > # expected: '/root > # ' > # Looks like you failed 2 tests of 34. > > I resolved the matter by simply renaming the file, but I would > recommend to filter out such pathologically named files > before calling Cwd::fast_abs_path($file) or > Cwd::fast_abs_path($file) at least in t/cwd.t . > > Kind regards, > Alexander Haeckel >
I can't tell from your report which were the two tests that failed. Would it be possible for you to simulate the original problematic file by testing the Perl 5 blead (which contains what is now dist/Cwd/t/cwd.t)? Thank you very much. Jim Keenan


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.