untraceable uninit warnings

[Graham Barr <gb...@valueclick.com>]

Does anyone have any idea what could be causing 

Use of uninitialized value at PerlHandler subroutine `VC::Delivery::Cycle::handler' line 1.

to appear in the errorlog ?

I even added

local $SIG{__WARN__} = sub { warn "here" };

as the first line of VC::Delivery::Cycle::handler, but it never gets
triggered, so it would seem the uninit is before the sub is called.

The strange thing is that it is only this one handler that causes
such a warning, all others are fine.

Thanks,
Graham.

Re: untraceable uninit warnings

[Graham Barr <gb...@valueclick.com>]

Ah, this was a while ago,

I did actually trace the problem down. The handler was returning undef
which was causing these warnings. It was just not taht obvious from the
warning given.

Graham.

On Thu, Jun 14, 2001 at 09:48:42AM -0700, Doug MacEachern wrote:
> On Wed, 7 Mar 2001, Graham Barr wrote:
> 
> > Does anyone have any idea what could be causing 
> > 
> > Use of uninitialized value at PerlHandler subroutine `VC::Delivery::Cycle::handler' line 1.
> > 
> > to appear in the errorlog ?
> > 
> > I even added
> > 
> > local $SIG{__WARN__} = sub { warn "here" };
> > 
> > as the first line of VC::Delivery::Cycle::handler, but it never gets
> > triggered, so it would seem the uninit is before the sub is called.
> > 
> > The strange thing is that it is only this one handler that causes
> > such a warning, all others are fine.
> 
> this will only happen if you gave Makefile.PL PERL_MARK_WHERE=1
> which will modify CopFILEGV(curcop) if Perl doesn't know what it is for
> some reason.  not sure why the WARN hook is being ignored, if you can
> whittle it down to a small test case i will have a look.
> 

Re: untraceable uninit warnings

[Doug MacEachern <do...@covalent.net>]

On Wed, 7 Mar 2001, Graham Barr wrote:

> Does anyone have any idea what could be causing 
> 
> Use of uninitialized value at PerlHandler subroutine `VC::Delivery::Cycle::handler' line 1.
> 
> to appear in the errorlog ?
> 
> I even added
> 
> local $SIG{__WARN__} = sub { warn "here" };
> 
> as the first line of VC::Delivery::Cycle::handler, but it never gets
> triggered, so it would seem the uninit is before the sub is called.
> 
> The strange thing is that it is only this one handler that causes
> such a warning, all others are fine.

this will only happen if you gave Makefile.PL PERL_MARK_WHERE=1
which will modify CopFILEGV(curcop) if Perl doesn't know what it is for
some reason.  not sure why the WARN hook is being ignored, if you can
whittle it down to a small test case i will have a look.