good chemistry is complicated,
and a little bit messy -LW
Building perl from source is quite easy assuming you have an appropriate compiler.
For consistency and simplicity, I'd recommend using the MS free edition.
Once you've installed the compiler, download the active state source code for your version of perl.
Gunzip the *.source.tar.gz. Edit the win32\Makefile to set the compiler (CC) and install directories and then do nmake Makefile and go to lunch. When you return you should be able to do nmake test, and if your company would object to you taking another lunch you could do some work for an hour. Preferably on another machine :)
Then nmake install. Then install any non-core dependencies required by your application, and the application itself. At that point you should be able to run the application.
Once you have it running, you can then tweak the source code where the message is produced, re-build, and then try to recreate the failure with the benefit of whatever extra information you've added.
I'd suggest adding at least the threadid and caller information. It should also be possible to discover the name of the perl-level cond-var that is giving the problem. That lot should go quite a way to helping you track down the source of the problem.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.