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

Posted to notifications@logging.apache.org by "Robert Middleton (Jira)" <lo...@logging.apache.org> on 2021/03/11 02:08:00 UTC

[jira] [Resolved] (LOGCXX-517) Circular reference in ErrorHandlerTestCase

     [ https://issues.apache.org/jira/browse/LOGCXX-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Middleton resolved LOGCXX-517.
-------------------------------------
    Resolution: Fixed

> Circular reference in ErrorHandlerTestCase
> ------------------------------------------
>
>                 Key: LOGCXX-517
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-517
>             Project: Log4cxx
>          Issue Type: Bug
>            Reporter: Robert Middleton
>            Assignee: Robert Middleton
>            Priority: Major
>             Fix For: 0.12.0
>
>
> For the smart pointer implementation, when GCC's sanitizers are enabled(fsanitize=leak), all tests pass except for the ErrorHandlerTestCase, which uses the FallbackErrorHandler.
>  
> Likely this is due to a circular reference with the shared_ptrs. 
>  
> This may be cleanly done with an API-breaking change.  The issue is that when using the DOM configurator, as soon as the XML file loads, it will attempt to open an invalid file, triggering the FallbackErrorHandler.  The FallbackErrorHandler then removes the appender, and adds a new one.  It seems that it should either propagate this error up, or replace the returned appender, instead of trying to replace the appender.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)