That's not a warning, that's a fatal error. If you want to catch fatal errors, there's a few things you can do:

1. Put a handler in $SIG{__DIE__}. You will get the fatal error message but the program will still die. (Unless you do some extra work. See the perlvar entry on %SIG for details.)

2. Wrap your possible fatality-producing code in an eval. Any fatal error will be put in $@ which you can send to your logging function. For example: 

eval { 
    $self->NonExistingFunction();
};

print "FATAL ERROR: $@" if $@;

[download]

In reply to Re: Catching warnings by friedo
in thread Catching warnings by Marcello

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.