Home     |     .Net Programming    |     cSharp Home    |     Sql Server Home    |     Javascript / Client Side Development     |     Ajax Programming

Ruby on Rails Development     |     Perl Programming     |     C Programming Language     |     C++ Programming     |     IT Jobs

Python Programming Language     |     Laptop Suggestions?    |     TCL Scripting     |     Fortran Programming     |     Scheme Programming Language


 
 
Cervo Technologies
The Right Source to Outsource

MS Dynamics CRM 3.0

Perl Programming Language

FAQ 9.3 How can I get better error messages from a CGI program?


This is an excerpt from the latest version perlfaq9.pod, which
comes with the standard Perl distribution. These postings aim to
reduce the number of repeated questions as well as allow the community
to review and update the answers. The latest version of the complete
perlfaq is at http://faq.perl.org .

--------------------------------------------------------------------

9.3: How can I get better error messages from a CGI program?

    Use the CGI::Carp module. It replaces "warn" and "die", plus the normal
    Carp modules "carp", "croak", and "confess" functions with more verbose
    and safer versions. It still sends them to the normal server error log.

        use CGI::Carp;
        warn "This is a complaint";
        die "But this one is serious";

    The following use of CGI::Carp also redirects errors to a file of your
    choice, placed in a BEGIN block to catch compile-time warnings as well:

        BEGIN {
            use CGI::Carp qw(carpout);
            open(LOG, ">>/var/local/cgi-logs/mycgi-log")
                or die "Unable to append to mycgi-log: $!\n";
            carpout(*LOG);
        }

    You can even arrange for fatal errors to go back to the client browser,
    which is nice for your own debugging, but might confuse the end user.

        use CGI::Carp qw(fatalsToBrowser);
        die "Bad error here";

    Even if the error happens before you get the HTTP header out, the module
    will try to take care of this to avoid the dreaded server 500 errors.
    Normal warnings still go out to the server error log (or wherever you've
    sent them with "carpout") with the application name and date stamp
    prepended.

--------------------------------------------------------------------

The perlfaq-workers, a group of volunteers, maintain the perlfaq. They
are not necessarily experts in every domain where Perl might show up,
so please include as much information as possible and relevant in any
corrections. The perlfaq-workers also don't have access to every
operating system or platform, so please include relevant details for
corrections to examples that do not work on particular platforms.
Working code is greatly appreciated.

If you'd like to help maintain the perlfaq, see the details in
perlfaq.pod.

--
Posted via a free Usenet account from http://www.teranews.com

Add to del.icio.us | Digg this | Stumble it | Powered by Megasolutions Inc