in reply to Re: Re: Strange problems with CGI script
in thread Strange problems with CGI script

Due to various issues people have with error logs, you shoud really debug from the commandline, especially for compile time errors.

You should also familiarize yourself with CGI::Carp (great for run time errors). I'm quite fond of keeping my own log, something resembling

BEGIN { use CGI::Carp qw( fatalsToBrowser ); CGI::Carp::carpout(\*LOGGY) if open(LOGGY, '>>'.__FILE__.'.err.log'); }


MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: Re: Re: Strange problems with CGI script
by Wassercrats (Initiate) on Jan 28, 2003 at 10:00 UTC
    That's the best advice I've received (and will take) in a long time! I wish I knew that along time ago! Recently, my web host's server didn't return a fatal error in the error log, but I assumed that was just a web host thing. When others programmers couldn't find this one (and I know they tried), I figured there was no error that would stop execution.