You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@logging.apache.org by "Ben Siron (JIRA)" <ji...@apache.org> on 2017/07/23 02:45:01 UTC

[jira] [Created] (LOG4NET-570) ILogExtensions don't preserve stack trace of caller

Ben Siron created LOG4NET-570:
---------------------------------

             Summary: ILogExtensions don't preserve stack trace of caller
                 Key: LOG4NET-570
                 URL: https://issues.apache.org/jira/browse/LOG4NET-570
             Project: Log4net
          Issue Type: Improvement
          Components: Other
    Affects Versions: 2.0.8
            Reporter: Ben Siron
            Priority: Minor


If you use a PatternLayout key such as %file or %method and use any of the ILogExtensions methods, the file and method (and any other info which should be showing the caller's stack frame) which are output are that of the ILogExtensions extension method rather than of the stack frame above it (the code that called ILogExtensions).

I could supply code to fix this via a pull request which would involve calling the lower level log method directly with the appropriate stack boundary type.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)