I have the same problem with perl 5.10.1 under linux, but not with the original code, that works:

CMD : >>echddo 'arghh'<< RETURN_CODE: >>32512<< CMD_RESULT : >>sh: echddo: command not found <<

However, I want to trap an error from a simple command, but a bad one. For example, a misspelled command:

my $cmd = "hostnam";

Here I can't trap the error:

CMD : >>hostnam<< RETURN_CODE: >>-1<< CMD_RESULT : >><<

The odd thing is that if I redirect STDOUT/STDERR to a file instead, the error is redirected as expected.

`$cmd 1>./tmp 2>&1`; my $cmd_rc = $?; my $cmd_result = `cat ./t`;
CMD : >>hostnam<< RETURN_CODE: >>32512<< CMD_RESULT : >>sh: hostnam: command not found <<

Is there a better way to get the expected behavior without resorting to a file?


In reply to Re: Unable to grab STDERR from a backtick command by tbartold
in thread Unable to grab STDERR from a backtick command by reasonablekeith

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.