you're right, i forgot about those two perl signals.
ashamed
martin
Stas Bekman wrote:
> Martin Haase-Thomas wrote:
>
>> perl sighandlers require the signal as their first argument. so i
>> assume that it may not be a good idea to call Carp::cluck(), as any
>> of the Carp methods expect strin
Martin Haase-Thomas wrote:
> perl sighandlers require the signal as their first argument. so i assume
> that it may not be a good idea to call Carp::cluck(), as any of the Carp
> methods expect strings. try typing as follows:
>
> $SIG{WARN} = sub { Carp::cluck ("received signal shift() at
> li
perl sighandlers require the signal as their first argument. so i assume
that it may not be a good idea to call Carp::cluck(), as any of the Carp
methods expect strings. try typing as follows:
$SIG{WARN} = sub { Carp::cluck ("received signal shift() at
line".__LINE__) };
martin
Tim Noll wro
Stas Bekman wrote:
> > I know this is a pretty generic question, but if nobody knows a quick
> > answer, I can get more specific in a later post. Under Apache 1.3.22 /
> > mod_perl 1.26, even while using $SIG{__WARN__} = \&Carp::cluck, I keep
> > getting "Use of uninitialized value." in the Apache
Tim Noll wrote:
> I know this is a pretty generic question, but if nobody knows a quick
> answer, I can get more specific in a later post. Under Apache 1.3.22 /
> mod_perl 1.26, even while using $SIG{__WARN__} = \&Carp::cluck, I keep
> getting "Use of uninitialized value." in the Apache error log,
I know this is a pretty generic question, but if nobody knows a quick
answer, I can get more specific in a later post. Under Apache 1.3.22 /
mod_perl 1.26, even while using $SIG{__WARN__} = \&Carp::cluck, I keep
getting "Use of uninitialized value." in the Apache error log, with
absolutely no line
