Guten Tag Thorsten Schöning,
am Freitag, 15. Oktober 2010 um 12:53 schrieben Sie:
is there any way to get the method name of the logging caller in the
log message? In some places %M is mentioned, but it doesn't seem to
work and is not in the documentation of class PatternLayout.
Hello,
%M is
If you are using the LOG4CXX_DEBUG and similar macros and some of the more
popular compilers, then you hopefully will get class and method information.
If you transliterated java code and are just doing logger.debug(Msg), then
that information is not available to you.
The performance issue
Guten Tag Curt Arnold,
am Montag, 18. Oktober 2010 um 15:14 schrieben Sie:
If you are able to see file and line, but not class and method,
then explore extending __LOG4CXX_FUNC__ to support your compiler.
Thanks for the hint, but even if I do that, I just get what %l would
print, right? It
Hello,
is there any way to get the method name of the logging caller in the
log message? In some places %M is mentioned, but it doesn't seem to
work and is not in the documentation of class PatternLayout. With
log4perl and log4j I'm able to log the whole class path down to a
method and wondered
On 10/15/2010 5:53 AM, Thorsten Schöning wrote:
Hello,
is there any way to get the method name of the logging caller in the
log message?
As you say, the log4j docs document %M in the PatternLayout (while
log4cxx does not) but caution against the inefficiency of it's use.
Additionally The
