To expand on this to make it a bit more useful: 

$SIG{__WARN__} = \&_warn_mess;

sub _warn_mess
{
  require Carp;
  print STDERR Carp::longmess(@_);
}

[download]
This prints out the stack trace at the point of the warning - which I think is what will help the OP the most. I know I've gotten a lot of use out of that to the point where I've put it in its own module at work and can just use it when I need the help ;-)

Update: Missed the extra underscores on __WARN__ and the print for the longmess - thanks to Hue-Bond for alerting me

In reply to Re^2: trapping "uninit" warnings to get more info by Tanktalus
in thread trapping "uninit" warnings to get more info by millardjk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.