The CGI::Carp idea is good. If you don't want to output errors to your web pages, just use Carp; (croak ~ die, carp ~ warn ) to get stacktraces output to the error logs.
Also, the error logs may be in a few places, depending on the system you're working on. Look in /etc/httpd/logs/ or /var/log/httpd. If you think there's something more going on, try:
%> cat /etc/httpd/conf*/*.conf | grep -i Log
You'll get a list of all the mentions of logging in the conf and conf.d files.
Also, when you check code with perl -c, put in all the options you would normally put on the #! line. For example, you may want to use:
%> perl -cwT some.cgi
And lastly, use __FILE__ and __LINE__ if you're having trouble inside of if statements. These always work (in my experience... nothing really -always- works).
if( 1 ){
&foo || die "$! at " . __FILE__ . "-" . __LINE__ ;
}
I hope this helps. Good luck!
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.