And with a simple package such as 
package SIGS;

# We're going to use Carp so we can get longmess
use Carp;
use if (scalar grep {m{Carp}} (keys %INC)), "Carp::Heavy";

# Now redefine Carp::format_arg so we can dump refs too!
    no warnings qw(once redefine);
    *Carp::format_arg = sub {
        package Carp;
        my $arg=shift;

        if (not defined $arg) {
            $arg='undef';
             }
        elsif (ref $arg) { # we'll use Data::Dumper
            require Data::Dumper;
            #no warnings qw(once);
            local $Data::Dumper::Indent=0;
            local $Data::Dumper::Terse=0;
            #use warnings;
            $arg=Data::Dumper::Dumper($arg);
            $arg=~ s/^\$VAR\d+\s*=\s*//;
            $arg=~ s/;\s*$//;
             }
        else {
            $arg=~ s/'/\\'/g;
            #no warnings qw(once);
            $arg=str_len_trim($arg,$Carp::Heavy::MaxArgLen);
            #use warnings;
            $arg="'$arg'" unless $arg =~ /^-?[\d.]+\z/;
             }
        $arg=~ s/([[:cntrl:]]|[[:^ascii:]])/sprintf("\\x{%x}",ord($1))
+/eg;
        return $arg;
         } if (scalar grep {m{^Carp}} (keys %INC));
    use warnings;

use strict;
use warnings;

# Someplace to put messages
our (@Messages);

INIT {
    ### program INIT ...
    close(STDERR);
    open(STDERR,'>','nul') or die "";
    $SIG{__WARN__}= sub {
        return unless (defined($main::DEBUG) and $main::DEBUG);
        # Carp's longmess includes the at ... line ... so remove it fr
+om $_[-1]
        my @a=@_;
        $a[-1]=~ s/ at .+? line \d+.$//s;
        # Save message and traceback
        push(@Messages,@a,Carp::longmess());
        # and warn --- output goes to nul
        warn @_;
         };
    $SIG{__DIE__}= sub {
        # Carp's longmess includes the at ... line ... so remove it fr
+om $_[-1]
        my @a=@_;
        $a[-1]=~ s/ at .+? line \d+.$//s;
        # Save message and traceback
        push(@Messages,@a,Carp::longmess());
        # and die --- output goes to nul and dies
        die @_;
         };
     } # INIT;

END {
    ### program END ...
    close(STDERR);
    if ($?) {
        # email @Messages from here
        print "Emailing these messages:\n";
        print @Messages;
         };
     } # END;

    0 == 0;

[download]
you can make 
use strict;
use warnings;

    sub A {
        ((1 x shift) !~  m{^(11+)\1+$}) or die "argument is not prime"
+;
        A(@_);
         };
    warn "\$DEBUG testing!";
    A(1,2,3,4,5);
    exit;

[download]
cough up 
Emailing these messages:
argument is not prime
 at SIGS.pl line 16
        main::A(4, 5) called at SIGS.pl line 17
        main::A(3, 4, 5) called at SIGS.pl line 17
        main::A(2, 3, 4, 5) called at SIGS.pl line 17
        main::A(1, 2, 3, 4, 5) called at SIGS.pl line 20

[download]
by using the -m option.

In reply to Re^2: using warn instead or print STDERR? by Anonymous Monk
in thread using warn instead or print STDERR? by leocharre

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.