[jira] [Resolved] (LOGCXX-205) SyslogWriterTest, InetAddressTestCase and OptionConverterTestCase cause valgrind to report invalid reads inside apr calls.

["Thorsten Schöning (Jira)" <lo...@logging.apache.org>]

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

Thorsten Schöning resolved LOGCXX-205.
--------------------------------------
    Resolution: Cannot Reproduce

Because we are trying to reduce the backlog of open issues, I'm closing this one right now. The described environment in which the problem has been reported originally is pretty outdated these days and things might have been fixed already with a newer version of log4cxx and/or a new environment. If this concrete problem is still relevant for someone, feel free to reopen and provide the necessary details. Otherwise it's best to create a new issue describing the new environment and problem.

> SyslogWriterTest, InetAddressTestCase and OptionConverterTestCase cause valgrind to report invalid reads inside apr calls.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOGCXX-205
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-205
>             Project: Log4cxx
>          Issue Type: Bug
>          Components: Appender
>         Environment: Ubuntu 7.10 VM on VMWare Fusion
>            Reporter: Curt Arnold
>            Assignee: Curt Arnold
>            Priority: Major
>         Attachments: log4cxx.28828, log4cxx.29516
>
>
> Running the ant built log4cxx-test on Ubuntu 7.10 under Valgrind reports invalid reads deep underneath apr calls.  See attached reports.  Only one obvious problem in the log4cxx code.  Possibly an APR issue, so test should be rerun with later APR's and OS packaged APR's to see if reports persist.  If unable to diagnose, should package up test case and ask apr-dev to look at issue.
> Had thought that issues might be the cause of other mysterious test failures (likely to be LOGCXX-206), but disabling the three mentioned tests did not cause the other test failures to go away.



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