If you don't need to know which parts are from stderr, and which are from stdout, i would suggest appending 2>&1 to your command. This will cause the unix shell to rediect them both so you can read them.

On the other hand, if they have to be seperate, i would suggest :
  1. using pipe() twice
  2. fork()'ing off a child.
  3. Using open() in the child to reset STDOUT and STDERR to the writing ends of the pipes.
  4. using exec() in the child to start the command
  5. let the parent (from the fork()) read the other ends of the pipes, and process them seperatly.

... just a thought.
i had a memory leak once, and it ruined my favorite shirt.

In reply to Re: "Exception" handling and more... by MZSanford
in thread "Exception" handling and more... by r.joseph

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.