使用未初始化的值和回调退出

Use of uninitialized value at (eval 80) line 12. 在（EVAL 80）第12行使用未初始化的值

Your code includes some undefined variable that you have used as if it was already defined and initialized.

你的代码包括一些未定义的变量,你作为已经定义并初始化的来使用。

For example: 例如:
$param = $q->param(’test’);
print $param;
vs.
$param = $q->param(’test’) || ’’;
print $param;

In the second case, $param will always be defined, either with $q->param(’test’)’s return value or the default value (’ empty string in our example).

在第二种情况下，$参数总是会被定义，无论是$Q->参数的返回值或默认值（“”在我们的例子中的空字符串）。

Also read about Finding the Line Which Triggered the Error or Warning. 因此也找到引发错误或警告的行。

Callback called exit 调用的回调退出

Callback called exit is just a generic message when some unrecoverable error occurs inside Perl during perl_call_sv() (which mod_perl uses to invoke all handler subroutines. Such problems seem to occur far less with 5.005_03 than 5.004.

调用的回调退出是一个通用的消息，这仅仅是在Perl的perl_call_sv()执行中一些不可恢复的错误出现时产生(perl_call_sv()是mod_perl用于调用所有处理程序子例程）。这些问题似乎发生在5.005 _03的次数远远少于5.004。

Sometimes you discover that your server is not responding and its error_log has filled up the remaining space on the file system. When you get to see the contents of the error_log -- it includes millions of lines, Callback called exit at -e line 33, <HTML> chunk 1. 有时你会发现你的服务器没有响应，并且其error_log填满文件系统剩下的空间。当你看到error_log的内容——它包括数百万行，回调退出 -e line 33, <HTML> chunk 1。

Why the looping? 为什么循环?

Perl can get very confused inside an infinite loop in your code. It doesn’t necessarily mean that your code did call exit(). Perl’s malloc went haywire and called croak(), but no memory is left to properly report the error, so Perl is stuck in a loop writing that same message to stderr.

Perl在一个无限循环的代码中会非常混乱。这并不一定意味着你的代码没有调用exit()。Perl的函数失控，叫做croak()，但适当的报告错误无法储存，所以Perl在同一个错误中死循环。

Perl 5.005+ plus is recommended for its improved malloc.c and other features that improve mod_perl and are turned on by default Perl 5.005+ plus建议改善malloc。其他改善的mod_perl的功能在默认情况下被打开。

友情链接

汕头招聘网 | 山东招聘网 | 郑州教育培训 | 软件下载