I've never seen someone try to use set_die_handler, so if you're trying to do it all yourself, forget all about CGI::Carp and use do

BEGIN { $main::SIG{__DIE__} = \&extra_special_die_handler; }

The double/output is bugs in CGI::Carp

its either inadequate documentation explaining how to best use this feature

logic error in "sub CGI::Carp::die" in that it realdie's after calling die_handler even though that will just call diehandler again

no signal/sentinel to die_handler that its being called by realdie

or still overriding CORE::die with CGI::Carp::die despite using set_die_handler, so having die_handler get called twice

 

could be argued (i feel) set_die_handler should not exist at all -- $main::SIG{__DIE__} is known/documented in perlvar


In reply to Re: Duplicate CGI::Carp Output ( set_die_handler, $main::SIG{__DIE__} ) by Anonymous Monk
in thread Duplicate CGI::Carp Output by InfiniteSilence

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.