Here are two things that should help immensely with debugging your CGI scripts...

First, before you upload your script to the web server, make sure it compiles: perl -c myscript.cgi

Second, use CGI::Carp to get more useful output when your script dies: use CGI::Carp qw/ fatalsToBrowser /; CGI::Carp by itself will produce nicely formatted error messages in the server's error log. Importing fatalsToBrowser will cause those errors to be sent to the browser as well.

You can also use CGI::Carp's carpout method to create your own private error log in an easily accessible place, rather than using the server's.

In reply to Re: Re: Re: Re: Re: for loop over large BLOCK keeps failing by chipmunk
in thread for loop over large BLOCK keeps failing by cdherold

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.