You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by Newtopian <gi...@git.apache.org> on 2015/03/11 22:13:29 UTC

[GitHub] log4net pull request: Fixed stackoverflow when logging internal

GitHub user Newtopian opened a pull request:

    https://github.com/apache/log4net/pull/14

    Fixed stackoverflow when logging internal

    When internal logging is on, manually shutdown and stderr/stdout
    redirection is performed in log4net we get infinite loop.  This fixes
    the stack overflow but does not fix the fact that logging is done after
    the hierarchy was shutdown

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Newtopian/log4net trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/log4net/pull/14.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #14
    
----
commit 790ba0a3cd99a59cb3d3f20737a5407d5bb4b5b1
Author: Éric Daigneault <sa...@gmail.com>
Date:   2015-03-11T21:12:17Z

    Fixed stackoverflow when loggin internal
    
    When internal logging is on, manually shutdown and stderr/stdout
    redirection is performed in log4net we get infinite loop.  This fixes
    the stack overflow but doe snot fix the fact that logging is done after
    the hierarchy was shutdown

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] log4net pull request: Fixed stackoverflow when logging internal

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/log4net/pull/14


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---