From another forum I have learned that perldb requires STDOUT to be a terminal, so that the ">../to_excel/excnnnnn.txt" in my invocation line caused my problem. This would not have to be the case: the writer on the site where I learned about this feature noted that perldb could find the terminal from any of STDIN, STDOUT, or STDERR, whichever was not redirected.

SUGGESTION FOR FUTURE WORK ON perldb!!

As it is, I will revise the program to open and use the output file named in ARGV[0], and leave my command line unchanged except for replacing '>' with a space.

In reply to Re^3: debug startup problem by cmac
in thread debug startup problem by cmac

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.