finding errors in utilcmd_out.log

nipper

I have a bunch of these (I may get 100-200 at one shot)

Use of uninitialized value in numeric eq (==) at (eval 88) line 1394.
Use of uninitialized value in substitution (s///) at (eval 88) line 1265.

in my util log.

I am even having a heck of a time nailing down what is running when this happens. I cannot replicate it on demand.

None of my PMs or scripts have that many lines. I use XMLNode but those line #s are comments.

I have tried to generate HTML from my TPLs and cannot make them show up, so I am guessing they are not in the TPL (but certainly could be), however those line #s are much larger than other TPL caused errors I have seen.

So, what choice do I have ? Deal with it ? Ideas ?

Adam Stoller

I have a bunch of these (I may get 100-200 at one shot) Use of uninitialized value in numeric eq (==) at (eval 88) line 1394. Use of uninitialized value in substitution (s///) at (eval 88) line 1265. in my util log. I am even having a heck of a time nailing down what is running when this happens. I cannot replicate it on demand. None of my PMs or scripts have that many lines. I use XMLNode but those line #s are comments. I have tried to generate HTML from my TPLs and cannot make them show up, so I am guessing they are not in the TPL (but certainly could be), however those line #s are much larger than other TPL caused errors I have seen. So, what choice do I have ? Deal with it ? Ideas ?

For each of your custom Perl scripts (workflow, custom menu items, iwat triggers, call servers, etc.) - from the command line, run them with:

iwperl -w -c script

If you don't find the issue to fix there - check embedded code in your WFTs and/or PTs.