Comments on: CentOS/RHEL x86_64 + VMWare: Use of uninitialized value in string http://rackerhacker.com/2008/09/03/centosrhel-x86_64-vmware-use-of-uninitialized-value-in-string/ Words of wisdom from a server administrator Mon, 21 May 2012 12:07:17 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Andy http://rackerhacker.com/2008/09/03/centosrhel-x86_64-vmware-use-of-uninitialized-value-in-string/#comment-15632 Andy Thu, 10 Dec 2009 14:05:02 +0000 http://rackerhacker.com/?p=366#comment-15632 Thanks BigJoe. Watch out though, folks. The text above includes those pesky 'smart double quotes', not real double-quotes, so you'll need to replace the incorrect double-quotes with correct ones when you paste this snippet in to the Perl module. Thanks BigJoe.

Watch out though, folks. The text above includes those pesky 'smart double quotes', not real double-quotes, so you'll need to replace the incorrect double-quotes with correct ones when you paste this snippet in to the Perl module.

]]> By: BigJoe http://rackerhacker.com/2008/09/03/centosrhel-x86_64-vmware-use-of-uninitialized-value-in-string/#comment-2597 BigJoe Wed, 03 Sep 2008 18:56:13 +0000 http://rackerhacker.com/?p=366#comment-2597 This assumption is probably true that this won't cause any errors. But after patching and upgrading this could come up to haunt you. This is essentially dying because one or both of the two values in evaluation are not defined. A potentially safer way to fix this is to add the following can make a minor change: $VERSION = "0" if(! defined($VERSION)); my $APIVERSION = version(); $APIVERSION = "0" if(! defined($APIVERSION)); die "Perl API Version does not match dynamic library version." unless ($APIVERSION eq $VERSION); Sorry for my randomly nuts rant but this error is one of my biggest pet peeves from maintaining and troubleshooting existing Perl code. It bugs me even more that code like this is distributed and generates all these errors making administrators think that all Perl code is buggy or unstable. This assumption is probably true that this won't cause any errors. But after patching and upgrading this could come up to haunt you. This is essentially dying because one or both of the two values in evaluation are not defined. A potentially safer way to fix this is to add the following can make a minor change:

$VERSION = "0" if(! defined($VERSION));
my $APIVERSION = version();
$APIVERSION = "0" if(! defined($APIVERSION));

die "Perl API Version does not match dynamic library version."
unless ($APIVERSION eq $VERSION);

Sorry for my randomly nuts rant but this error is one of my biggest pet peeves from maintaining and troubleshooting existing Perl code. It bugs me even more that code like this is distributed and generates all these errors making administrators think that all Perl code is buggy or unstable.

]]>