Something that might work (maybe), would be to open like this: 
open( FILE, "$command 2>&1 |" );

[download]
What that does (if it works) is to put both STDERR and STDOUT together into the pipe. But then you have to know how to separate the error output from the non-error output, which might be a problem... (There shouldn't be any problem with lines being broken, but the relative ordering of stderr lines vs. stdout lines is not likely to be predictable or even consistent.)

I have a suspicion that it might not work on all OS's -- it should work on any unix-like system.)

In reply to Re: Capturing stderr from a test script executed by Test::Harness::Straps by graff
in thread Capturing stderr from a test script executed by Test::Harness::Straps by DrWhy

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.