Subject: | PERL_DL_NONLAZY definition causes continual errors |
Date: | Mon, 06 Dec 2010 15:22:42 -0500 |
To: | "bug-List-MoreUtils [...] rt.cpan.org" <bug-List-MoreUtils [...] rt.cpan.org> |
From: | "Tosh, Michael J" <michael.j.tosh [...] lmco.com> |
The following error is seen continuously in my HTTP Error log:
MoreUtils.pm: Use of uninitialized value in scalar assignment at lib/i386-linux-thread-multi/List/MoreUtils.pm line 24.
Looking at line 24, I see the following assignment:
local $ENV{PERL_DL_NONLAZY} = $ENV{PERL_DL_NONLAZY} ? 0 : $ENV{PERL_DL_NONLAZY};
Something about that line looks wrong. If Perl_DL_NONLAZY is non-zero, you set it to 0, otherwise you set it to undef? Why not just call out 'undef' instead? Although, setting it to undef also causes the same error.
Seems like a bug to me. Harmless, but certainly annoying. All I can seem to do to get rid of the error is to comment out the line completely. Maybe running under mod_perl in Apache causes $ENV to not get set?