A broken pipe does indeed send a fatal signal to your program. If you want the behaviour to be otherwise, there are a couple of decisions you first might have to make:

Firstly, whether to handle the signal as a warning or an error. For example, you could assign $SIG{ PIPE } to a handler that treats it as a warning, e.g.

$SIG{ PIPE } = sub { warn "Broken pipe trap, traceback follows:\n" . T
+race::trace(); }

[download]
The second decision of course being whether to use Devel::Trace as would be necessary for the above example, so that the signal handler reports where in the code it was invoked.

One world, one people

In reply to Re: unexpected program abort on write on closed handle by anonymized user 468275
in thread unexpected program abort on write on closed handle by Beechbone

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.