.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.TH CGI::Carp 3 "2002-06-01" "perl v5.8.0" "Perl Programmers Reference Guide"
\&\fBCGI::Carp\fR \- CGI routines for writing to the HTTPD (or other) error log
\& croak "We're outta here!";
\& confess "It was my fault: $!";
\& carp "It was your fault!";
\& use CGI::Carp qw(cluck);
\& cluck "I wouldn't do that if I were you";
\& use CGI::Carp qw(fatalsToBrowser);
\& die "Fatal error messages are now sent to browser";
\&\s-1CGI\s0 scripts have a nasty habit of leaving warning messages in the error
logs that are neither time stamped nor fully identified. Tracking down
the script that caused the error is a pain. This fixes that. Replace
And the standard \fIwarn()\fR, die (), \fIcroak()\fR, \fIconfess()\fR and \fIcarp()\fR calls
will automagically be replaced with functions that write out nicely
time-stamped messages to the \s-1HTTP\s0 server error log.
\& [Fri Nov 17 21:40:43 1995] test.pl: I'm confused at test.pl line 3.
\& [Fri Nov 17 21:40:43 1995] test.pl: Got an error message: Permission denied.
\& [Fri Nov 17 21:40:43 1995] test.pl: I'm dying.
.SH "REDIRECTING ERROR MESSAGES"
.IX Header "REDIRECTING ERROR MESSAGES"
By default, error messages are sent to \s-1STDERR\s0. Most \s-1HTTPD\s0 servers
direct \s-1STDERR\s0 to the server's error log. Some applications may wish
to keep private error logs, distinct from the server's error log, or
they may wish to direct error messages to \s-1STDOUT\s0 so that the browser
The \f(CW\*(C`carpout()\*(C'\fR function is provided for this purpose. Since
\&\fIcarpout()\fR is not exported by default, you must import it explicitly by
\& use CGI::Carp qw(carpout);
The \fIcarpout()\fR function requires one argument, which should be a
reference to an open filehandle for writing errors. It should be
called in a \f(CW\*(C`BEGIN\*(C'\fR block at the top of the \s-1CGI\s0 application so that
compiler errors will be caught. Example:
\& use CGI::Carp qw(carpout);
\& open(LOG, ">>/usr/local/cgi-logs/mycgi-log") or
\& die("Unable to open mycgi-log: $!\en");
\&\fIcarpout()\fR does not handle file locking on the log for you at this point.
The real \s-1STDERR\s0 is not closed \*(-- it is moved to CGI::Carp::SAVEERR. Some
servers, when dealing with \s-1CGI\s0 scripts, close their connection to the
browser when the script closes \s-1STDOUT\s0 and \s-1STDERR\s0. CGI::Carp::SAVEERR is there to
prevent this from happening prematurely.
You can pass filehandles to \fIcarpout()\fR in a variety of ways. The \*(L"correct\*(R"
way according to Tom Christiansen is to pass a reference to a filehandle
This looks weird to mere mortals however, so the following syntaxes are
\& carpout(\e'main::LOG');
FileHandle and other objects work as well.
Use of \fIcarpout()\fR is not great for performance, so it is recommended
for debugging purposes or for moderate-use applications. A future
version of this module may delay redirecting \s-1STDERR\s0 until one of the
CGI::Carp methods is called to prevent the performance hit.
.SH "MAKING PERL ERRORS APPEAR IN THE BROWSER WINDOW"
.IX Header "MAKING PERL ERRORS APPEAR IN THE BROWSER WINDOW"
If you want to send fatal (die, confess) errors to the browser, ask to
import the special \*(L"fatalsToBrowser\*(R" subroutine:
\& use CGI::Carp qw(fatalsToBrowser);
Fatal errors will now be echoed to the browser as well as to the log. CGI::Carp
arranges to send a minimal \s-1HTTP\s0 header to the browser so that even errors that
occur in the early compile phase will be seen.
Nonfatal errors will still be directed to the log file only (unless redirected
.Sh "Changing the default message"
.IX Subsection "Changing the default message"
By default, the software error message is followed by a note to
contact the Webmaster by e\-mail with the time and date of the error.
If this message is not to your liking, you can change it using the
\&\fIset_message()\fR routine. This is not imported by default; you should
import it on the \fIuse()\fR line:
\& use CGI::Carp qw(fatalsToBrowser set_message);
\& set_message("It's not a bug, it's a feature!");
You may also pass in a code reference in order to create a custom
error message. At run time, your code will be called with the text
of the error message that caused the script to die. Example:
\& use CGI::Carp qw(fatalsToBrowser set_message);
\& print "<h1>Oh gosh</h1>";
\& print "<p>Got an error: $msg</p>";
\& set_message(\e&handle_errors);
In order to correctly intercept compile-time errors, you should call
\&\fIset_message()\fR from within a BEGIN{} block.
.SH "MAKING WARNINGS APPEAR AS HTML COMMENTS"
.IX Header "MAKING WARNINGS APPEAR AS HTML COMMENTS"
It is now also possible to make non-fatal errors appear as \s-1HTML\s0
comments embedded in the output of your program. To enable this
feature, export the new \*(L"warningsToBrowser\*(R" subroutine. Since sending
warnings to the browser before the \s-1HTTP\s0 headers have been sent would
cause an error, any warnings are stored in an internal buffer until
you call the \fIwarningsToBrowser()\fR subroutine with a true argument:
\& use CGI::Carp qw(fatalsToBrowser warningsToBrowser);
\& use CGI qw(:standard);
You may also give a false argument to \fIwarningsToBrowser()\fR to prevent
warnings from being sent to the browser while you are printing some
content where \s-1HTML\s0 comments are not allowed:
\& warningsToBrowser(0); # disable warnings
\& print "<script type=\e"text/javascript\e"><!--\en";
\& print_some_javascript_code();
\& print "//--></script>\en";
\& warningsToBrowser(1); # re-enable warnings
Note: In this respect \fIwarningsToBrowser()\fR differs fundamentally from
\&\fIfatalsToBrowser()\fR, which you should never call yourself!
1.05 \fIcarpout()\fR added and minor corrections by Marc Hedlund
<hedlund@best.com> on 11/26/95.
1.06 \fIfatalsToBrowser()\fR no longer aborts for fatal errors within
1.08 \fIset_message()\fR added and \fIcarpout()\fR expanded to allow for FileHandle
1.09 \fIset_message()\fR now allows users to pass a code \s-1REFERENCE\s0 for
really custom error messages. croak and carp are now
exported by default. Thanks to Gunther Birznieks for the
1.10 Patch from Chris Dean (ctdean@cogit.com) to allow
module to run correctly under mod_perl.
1.11 Changed order of > and < escapes.
1.12 Changed \fIdie()\fR on line 217 to CORE::die to avoid \fB\-w\fR warning.
1.13 Added \fIcluck()\fR to make the module orthogonal with Carp.
More mod_perl related fixes.
1.20 Patch from Ilmari Karonen (perl@itz.pp.sci.fi): Added
\fIwarningsToBrowser()\fR. Replaced <\s-1CODE\s0> tags with <\s-1PRE\s0> in
\fIfatalsToBrowser()\fR output.
1.23 \fIineval()\fR now checks both $^S and inspects the message for the \*(L"eval\*(R" pattern
(hack alert!) in order to accomodate various combinations of Perl and
Copyright 1995\-2002, Lincoln D. Stein. All rights reserved.
This library is free software; you can redistribute it and/or modify
it under the same terms as Perl itself.
Address bug reports and comments to: lstein@cshl.org
Carp, CGI::Base, CGI::BasePlus, CGI::Request, CGI::MiniSvr, CGI::Form,
projects / OpenSPARC-T2-DV / blob