logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 44888] problem in showing Filename and Line number in log file
Date Thu, 15 May 2008 20:39:44 GMT

--- Comment #4 from Curt Arnold <carnold@apache.org>  2008-05-15 13:39:43 PST ---
Ralph, it sounds like you have an environment and sample app that reveals a
defect in the LocationInfo class.  It would be very helpful if you could
provide some insight into the defect so that could be understood.  Having a
work-around is good, but it would be better to understand the defect and try to
resolve it appropriately.

Could you provide any of the following info (the more, the better):

What platform are you running on (Windows, Mac, Linux, etc)?

Do the unit tests pass in your environment?

If the current tests pass, could you write a unit test that test the defective
code and fails?

If you can't write a unit test, could you write a sample app that demonstrates
the problem?

Can you step through the LocationInformation constructor and identify where and
why the location extraction code breaks down?  Previously this has been due to
a slightly different format of the output from printStackTrace, for example,
JRocket used spaces instead of tabs if I remember correctly.

Throwable.getStackTrace() was added in JDK 1.4, so depending on it would not be
consistent with log4j's targeting of JDK 1.3 or later.  However, it might be
tolerable to sniff for it using reflection or catch a MethodNotFound exception
and then fallback to the older code.

logback is licensed under the LGPL, so use of logback code without explicit
licensing from the original author is inconsistent with the ASF license and
can't go into log4j.  If the underlying problem is adequately identified, I'm
sure that we can come up with an appropriate solution without referring to the
logback code.

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message