Are you, by any chance, writing your binary data to your terminal? In that case the data might contain some control characters which cause the cursor to jump or other things, and as of 2018 your terminal is likely to expect UTF-8 encoded output. Also note that chomp is probably a bad idea on binary data.

For better diagnostics, you should apply binmode to your CMD filehandle and write the output to a file and examine this file.

Edited to add: I just spotted a 0a as the second byte of your bad stream. This is a line feed which will be killed by chomp.

In reply to Re: Killer byte tripping up Perl? by haj
in thread Killer byte tripping up Perl? by echo5

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.