On Sat Aug 13 16:21:21 2005, at@altlinux.ru wrote: > This is a bug report for perl from at@altlinux.org, > generated with the help of perlbug 1.35 running under perl v5.8.7. > > > $ perl -e 'use autouse qw(Pod::Usage pod2usage); pod2usage' > Can't open -e for reading: No such file or directory > at -e line 1 > $ perl -d:DProf -e 'use autouse qw(Pod::Usage pod2usage); pod2usage' > Can't open -e for reading: No such file or directory > at -e line 1 > zsh: segmentation fault (core dumped) > $ > Running your code on Darwin on Perl 5.14.2, I got the failure messages but no segmentation fault. ### [perl] 518 $ perl -e 'use autouse qw(Pod::Usage pod2usage); pod2usage' Can't open -e: No such file or directory at -e line 1 [perl] 519 $ perl -d:DProf -e 'use autouse qw(Pod::Usage pod2usage); pod2usage' Can't open -e: No such file or directory at -e line 1 ### But I should note that (a) Devel::DProf is deprecated -- see its documentation in Perl 5.14 -- so we're not fixing bugs in connection with it; and (b) even if we were still supporting DProf, I would be skeptical about it playing well with 'autouse'. After all, autouse's documentation includes these warnings: ### Using "autouse" will move important steps of your program's execution from compile time to runtime. This can o Break the execution of your program if the module you "autouse"d has some initialization which it expects to be done early. o hide bugs in your code since important checks (like correctness of prototypes) is moved from compile time to runtime. ... ### I wouldn't expect any profiler to play well with this. Thank you very much. Jim Keenan