Hi Steve,
It's a well known issue. See LOG4J_HOME/examples/subclass/MyLogger.java
(the comment before the FCQN variable.)
At 11:22 27.06.2002 -0500, Ebersole, Steven wrote:
>There is a real subtle bug in LocationInfo which can cause log4j itself to
>skip stack frames.
>
>It has to do with how t
-Original Message-
From: Tumpach, Andrew J [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 11:49 AM
To: Log4J Users List
Subject: RE: LocationInfo bug
Couldn't a similar problem occur with overloaded methods, where one is
called by another?
Andrew
-Original Me
Couldn't a similar problem occur with overloaded methods, where one is called by
another?
Andrew
-Original Message-
From: Ebersole, Steven [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 11:22 AM
To: Log4j user list (E-mail)
Subject: LocationInfo bug
There is a real s
There is a real subtle bug in LocationInfo which can cause log4j itself to
skip stack frames.
It has to do with how the stack trace is searched. In the current
LocationInfo.java at line 111, the following is executed:
ibegin = s.lastIndexOf(fqnOfCallingClass);
where 'fqnOfCallingClass' is su
