Also, what does a "normal" filename look like when printed?warn 'WARN:'.$self->filename; 97% ... WARN:(eval 657)[(eval 656)[/ExtUtils/MM_Unix.pm:2920]:1] at /D +evel/NYTProf/FileInfo.pm line 431. WARN:(eval 657)[(eval 656)[/ExtUtils/MM_Unix.pm:2920]:1] at /Devel/NYT +Prof/FileInfo.pm line 431. WARN: at /Devel/NYTProf/FileInfo.pm line 431. # NO FILENAME! Use of uninitialized value in numeric gt (>) at /Devel/NYTProf/Reader. +pm line 184. 98% ... WARN:(eval 1724)[/Module/Metadata.pm:13] at /Devel/NYTProf/Fil +eInfo.pm line 431. WARN:(eval 1724)[/Module/Metadata.pm:13] at /Devel/NYTProf/FileInfo.pm + line 431. 98% ... WARN:(eval 2699)[(eval 2698)[/Module/Metadata.pm:13]:6] at / +Devel/NYTProf/FileInfo.pm line 431. WARN:(eval 2699)[(eval 2698)[/Module/Metadata.pm:13]:6] at /Devel/NYTP +rof/FileInfo.pm line 431. WARN: at /Devel/NYTProf/FileInfo.pm line 431. # NO FILENAME! Use of uninitialized value in numeric gt (>) at /Devel/NYTProf/Reader. +pm line 184.
Either the it's the full path to a perl module, or one of those eval lines with parens and brackets.
Another question is why your code is using what appears to be a module installation process?
I'm using ExtUtils::Installed. ExtUtils::Installed::new calls ExtUtils::Installed::_make_entry which calls ExtUtils::MM_Unix::parse_version. Maybe I found another bug by analyzing Perl? (This time in NYTProf)
In reply to Re^7: NYTProf line report failure
by Anonymous Monk
in thread NYTProf line report failure
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |