It's hard to tell without seeing relevant code, but if the code was short enough likely you would have found the culprit already.

The intervening code might close STDOUT or use select to select a different filehandle:

sub nasty1 {
    close STDOUT;
}

nasty1();
print "everybody keep silent"; # maybe you get a warning that STDOUT w
+as closed

[download]
sub nasty2 {
    open my $fh, '>', 'output.txt' or die $!;
    select $fh; # everybody keep silent
    print "everybody keep silent"; # this shows up in 
}

nasty2();
print "everybody keep silent"; # this shows up in the output file

[download]

Maybe you did not properly create and open your debug filehandle.

Maybe the code that should print stuff never even gets called at all.

In reply to Re: print statements in perl pakages seem to be masked from STDOUT by Corion
in thread print statements in perl pakages seem to be masked from STDOUT by holandes777

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.