Mike Schilli wrote:
Thanks for the detailed description, here's what's happening:
This change in behavior was caused by a patch introduced with
Log-Log4perl-1.19 in
http://github.com/mschilli/log4perl/commit/35d86ae53859424ea3ac357eaf0f15d9e69f4bed
in September 2008. A detailed
Mike Schilli wrote:
Thanks for the detailed description, here's what's happening:
This change in behavior was caused by a patch introduced with
Log-Log4perl-1.19 in
http://github.com/mschilli/log4perl/commit/35d86ae53859424ea3ac357eaf0f15d9e69f4bed
in September 2008. A detailed
On Wed, 9 Dec 2009, Martin Evans wrote:
Since the upgrade we are getting no logging in one of the files we
expected to get it. After a bit of searching around I discovered the
module we were using was doing this:
local $Log::Log4perl::caller_depth = $Log::Log4perl::caller_depth + 1;
Mike Schilli wrote:
On Wed, 9 Dec 2009, Martin Evans wrote:
Since the upgrade we are getting no logging in one of the files we
expected to get it. After a bit of searching around I discovered the
module we were using was doing this:
local $Log::Log4perl::caller_depth =
