This queue is for tickets about the Win32-EventLog CPAN distribution.

Report information
The Basics
Id:
5498
Status:
open
Priority:
Low/Low

People
Owner:
Nobody in particular
Requestors:
rrwo [...] cpan.org
Cc:
AdminCc:

BugTracker
Severity:
Important
Broken in:
(no value)
Fixed in:
(no value)



Subject: Win32::EventLog "Use of uninitialized value in subroutine entry..." in Perl 5.8.2 ActiveState Build 808
Every time I post to the event log from Win32::EventLog::Carp, it gives the following errors for each $eventloghandle->Report() call: Use of uninitialized value in subroutine entry at C:/Perl/site/lib/Win32/EventLog.pm line 73. Use of uninitialized value in subroutine entry at C:/Perl/site/lib/Win32/EventLog.pm line 199. Use of uninitialized value in subroutine entry at C:/Perl/site/lib/Win32/EventLog.pm line 199. Use of uninitialized value in subroutine entry at C:/Perl/site/lib/Win32/EventLog.pm line 199. Use of uninitialized value in subroutine entry at C:/Perl/site/lib/Win32/EventLog.pm line 199. I've tested Win32::EventLog::Carp and modified it so that it does not call report with undefined values. My guess is that something changed in Perl 5.8 that Win32::EventLog is not friendly with.
From: nathan.waddell@fedex.com
There is no computer name or class being passed to Win32::EventLog as default values. I suggest Win32::NodeName() for the computer name, and just create an empty class. On Sun Feb 29 13:25:34 2004, guest wrote:
Show quoted text
> Every time I post to the event log from Win32::EventLog::Carp, it > gives the following errors for each $eventloghandle->Report() call: > > Use of uninitialized value in subroutine entry at > C:/Perl/site/lib/Win32/EventLog.pm line 73. > Use of uninitialized value in subroutine entry at > C:/Perl/site/lib/Win32/EventLog.pm line 199. > Use of uninitialized value in subroutine entry at > C:/Perl/site/lib/Win32/EventLog.pm line 199. > Use of uninitialized value in subroutine entry at > C:/Perl/site/lib/Win32/EventLog.pm line 199. > Use of uninitialized value in subroutine entry at > C:/Perl/site/lib/Win32/EventLog.pm line 199. > > I've tested Win32::EventLog::Carp and modified it so that it does not > call report with undefined values. My guess is that something changed > in Perl 5.8 that Win32::EventLog is not friendly with. >
From: nathan.waddell@fedex.com
The solution to this bug is as follows: Modify lines 205-210 to supress warnings. We *know* it's redefining the CORE module - that's the whole point of using this module. ORIGINAL LINEs 205 - 210: { sub carp { CORE::warn Carp::shortmess @_; } sub croak { CORE::die Carp::shortmess @_; } sub cluck { CORE::warn Carp::longmess @_; } sub confess { CORE::die Carp::longmess @_; } } RAVENHALL'S PATCH: { no warnings 'redefine'; sub carp { CORE::warn Carp::shortmess @_; } sub croak { CORE::die Carp::shortmess @_; } sub cluck { CORE::warn Carp::longmess @_; } sub confess { CORE::die Carp::longmess @_; } }
From: jand@activestate.com
On Tue Jun 20 19:13:25 2006, guest wrote:
Show quoted text
> The solution to this bug is as follows: > > Modify lines 205-210 to supress warnings. We *know* it's redefining
the
Show quoted text
> CORE module - that's the whole point of using this module. > > ORIGINAL LINEs 205 - 210: > { > sub carp { CORE::warn Carp::shortmess @_; } > sub croak { CORE::die Carp::shortmess @_; } > sub cluck { CORE::warn Carp::longmess @_; } > sub confess { CORE::die Carp::longmess @_; } > } > > RAVENHALL'S PATCH: > { > no warnings 'redefine'; > sub carp { CORE::warn Carp::shortmess @_; } > sub croak { CORE::die Carp::shortmess @_; } > sub cluck { CORE::warn Carp::longmess @_; } > sub confess { CORE::die Carp::longmess @_; } > }
This is actually a different set of warnings than the original report. You should report this patch in the Win32::EventLog::Carp queue because that module is not part of libwin32. Cheers, -Jan


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.