As implied in the CB, no matter how good you think your "recovery processes" may be in the production environment, I think it verges on idiocy errrr hiding your head in the sand to try to suppress what amounts to a warning that there's something seriously wrong.

Other, wiser Monks tried -- again in the CB -- to give you an approach with (IMHO) more merit. For example:
Corion 2006-12-06 11:06:39-05 I'd avoid Win32::Process and use system("start $that_process");. Of course you then lose control over the launched process.

tye offered another; and I may have missed a few folk who shared wisdom. I may also be missing the point/validity of your concern that the popups may go unanswered. My recommendation would be to monitor the production environment until I you found out what's borked.

So, please, tell us WHY you're not more interested in WHY Perl is crashing. Perhaps that info will help us respond more usefully (or (?) acceptably (?)

1Title changed -- new title lifted from a later remark-of-great-wisdom,-insight-and-frustration in the CB.

In reply to Thank you for not listening (<sup>1</sup>) Re: Prevent Perl Command Line Interpreter Popup From Appearing On Perl Crash by ww
in thread Prevent Perl Command Line Interpreter Popup From Appearing On Perl Crash by WAmaro

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.