Re: (forks) warnings from forks.pm

[email protected] (Elizabeth Mattijsen)
Newsgroups perl.ithreads
Message-ID <p05111b14bb9615576a22@[192.168.56.4]>
At 16:25 +0200 9/23/03, Per Buer wrote:
>I am getting quite a lot warnings from forks.pm;
>
>Use of uninitialized value in array element at 
>/usr/lib/perl5/forks.pm line 1143.
>Use of uninitialized value in array element at 
>/usr/lib/perl5/forks.pm line 1156.
>Use of uninitialized value in array element at 
>/usr/lib/perl5/forks.pm line 1143.
>Use of uninitialized value in array element at 
>/usr/lib/perl5/forks.pm line 1148.
>
>Is this a known issue? Is anyone interested in a back trace or something?
>
>I am using Perl 5.6.1 on i386, Debian Linux.

Ok, if you are using the most recent version of forks.pm, then this 
is bad.  It basically means that the ordinal number of the variable 
you're attempting to lock, is undefined.  I'd be interested to know 
how you are achieving this.

Could you try adding something like:

$SIG {__WARN__} = sub {require Carp; Carp::cluck()};

to your code so I can get a stacktrace of each of the warnings? 
Please send me these off list if you can.


Liz
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.