logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shash Chatterjee <schatter...@camber.com>
Subject log4cxx SIGSEGV in mutex_hash after program exit
Date Thu, 08 Apr 2010 15:09:00 GMT

I have seen this message
(http://objectmix.com/apache/745036-log4cxx-crashing-when-used-atexit-function.html), but
can't tell if there was/is a resolution.

I am having what looks like the same problem when my program exits,
here's the stack:

#0  0x002a6c07 in mutex_hash () at atomic/unix/mutex.c:78
#1  apr_atomic_dec32 (mem=0x8142ad4) at atomic/unix/mutex.c:138
#2  0x005303c5 in log4cxx::helpers::ObjectImpl::releaseRef
(this=0x8142ad0) at objectimpl.cpp:44
#3  0x0051bfb2 in log4cxx::Logger::releaseRef (this=0x0) at
#4  0x08054be9 in
log4cxx::helpers::ObjectPtrT<log4cxx::Logger>::~ObjectPtrT ()
#5  0x0013e949 in exit () from /lib/libc.so.6
#6  0x001266ed in __libc_start_main () from /lib/libc.so.6
#7  0x0804bda1 in _start ()

I am on Fedora 10, using kernel 2.6.27, gcc-4.3.2 (g++), log4cxx-0.10.0,
apr-1.3.9, apr-util-1.3.9.

Is there any any known workaround or a planned fix for this?

Thanks in advance,

View raw message