I'm suspicious of the "# Some more processing here which is not relevant" section after the more obvious suspects have been eliminated. Have you tried moving the "print Dumper($tref)'" inside your debugging if statement, to see if something in the loop might be sneaking extra entries into %{$tref}? You might also try printing the values of all the variables in the loop and the values of
exists $tref->{$host}{$test}{status}
and
defined $tref->{$host}{$test}{status}
inside that debugging if statement.
Murphy's law of debugging with print statements: the one value that is so redundant and predictable that you can eliminate any need to print it in your sleep is the one that contains the erroneous value. Unless you expected that to happen, in which case it won't.
In reply to Re: Tracking down an uninitialized value warning
by quester
in thread Tracking down an uninitialized value warning
by McDarren
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |