[jira] [Resolved] (LOGCXX-409) Crash in FileWatchDog::checkAndConfigure

["Joseph Southwell (JIRA)" <lo...@logging.apache.org>]

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

Joseph Southwell resolved LOGCXX-409.
-------------------------------------

    Resolution: Duplicate

> Crash in FileWatchDog::checkAndConfigure
> ----------------------------------------
>
>                 Key: LOGCXX-409
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-409
>             Project: Log4cxx
>          Issue Type: Bug
>            Reporter: joshila
>            Assignee: Curt Arnold
>
> We get occasional core dumps. I believe these happen when the application exits. We are using version 0.10.0 of log4cxx. Backtrace shown below:
> #0  apr_pool_create_ex (newpool=0x411b8fc0, parent=0x90121a8, abort_fn=0, allocator=0x900e090) at memory/unix/apr_pools.c:252
>  pool = <value optimized out>
>  node = (apr_memnode_t *) 0x8041
> #1  0x00002aec077de070 in Pool (this=0x411b8fc0) at pool.cpp:34
> No locals.
> #2  0x00002aec0779d8ef in log4cxx::helpers::FileWatchdog::checkAndConfigure (this=0x90f4750) at filewatchdog.cpp:47
>  pool1 = {pool = 0x0, release = true}
> #3  0x00002aec0779dca8 in log4cxx::helpers::FileWatchdog::run (data=<value optimized out>) at filewatchdog.cpp:79
>  pThis = (log4cxx::helpers::FileWatchdog *) 0x90f4750
>  interrupted = 151052472
> #4  0x00002aec07807ed8 in log4cxx::helpers::Thread::launcher (thread=0x90ed510, data=0x90ed4f8) at threadcxx.cpp:100
>  package = <value optimized out>
>  tls = <value optimized out>
>  alive = {alive = 0x90f47a0}
>  retval = <value optimized out>
> #5  0x0000003422c064a7 in start_thread () from /lib64/libpthread.so.0
> No symbol table info available.
> #6  0x00000034220d3c2d in clone () from /lib64/libc.so.6



--
This message was sent by Atlassian JIRA
(v6.2#6252)