Additional info (Without inadvertent Send Clicks early): This is the exception being caught in gdb and the backtrace of the stack at that point Program received signal SIGABRT, Aborted. 0xd0126af0 in pthread_kill () from /usr/lib/libpthread.a(shr_xpg5.o)
(gdb) bt #0 0xd0126af0 in pthread_kill () from /usr/lib/libpthread.a(shr_xpg5.o) #1 0xd01265b0 in _p_raise () from /usr/lib/libpthread.a(shr_xpg5.o) #2 0xd03395ac in raise () from /usr/lib/libc.a(shr.o) #3 0xd0367458 in abort () from /usr/lib/libc.a(shr.o) #4 0xd17b3a70 in apr_atomic_dec32 (mem=0x2000ef6c) at /mcoa300/shared/jfs2/src/RMI/Public/libs/log4cxx-0.9.8/lib/apr-1.2.2/ato mic/unix/apr_atomic.c:297 #5 0xd17acf40 in log4cxx::helpers: bjectImpl::releaseRef (this=0x2000ef68) at /mcoa300/shared/jfs2/src/RMI/Public/libs/log4cxx-0.9.8/src/objectimpl.cp p:39 #6 0xd17f4c98 in log4cxx::helpers: bjectPtrT<log4cxx::Level>::~ObjectPtrT (this=0xf0f61f68) at /mcoa300/shared/jfs2/src/RMI/Public/libs/log4cxx-0.9.8/include/log4cxx/h elpers/objectptr.h:88 #7 0xd17f6b30 in __static_initialization_and_destruction_0 (__initialize_p=0, __priority=65535) at /mcoa300/shared/jfs2/src/RMI/Public/libs/log4cxx-0.9.8/src/level.cpp:569 #8 0xd17f7160 in global destructors keyed to _ZNK7log4cxx5Level8getClassEv () at /mcoa300/shared/jfs2/src/RMI/Public/libs/log4cxx-0.9.8/src/level.cpp:214 #9 0xd1a1a918 in _GLOBAL__FD_liblog4cxx_so () from /mcoa300/shared/jfs2/src/RMI/Built/debug/ppc/liblog4cxx.so #10 0xd034f3ac in mod_fini1 () from /usr/lib/libc.a(shr.o) #11 0xd034f308 in modfini () from /usr/lib/libc.a(shr.o) #12 0xd034f8e8 in __modfini () from /usr/lib/libc.a(shr.o) #13 0xd0345e38 in exit () from /usr/lib/libc.a(shr.o) #14 0x100001f4 in __start () -----Original Message----- From: Ron Ohmer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 1:25 PM To: Andreas Fester; Log4CXX User Subject: RE: Core file on AIX Yeah, I guess that would be good.. ;-) Ok, Version AIX 5.3. GCC: Using built-in specs. Target: powerpc-ibm-aix5.3.0.0 Configured with: ../configure --prefix=/opt/RMI/AIX : (reconfigured) /tmp/gcc-4.0.2/configure : (reconfigured) ../configure --prefix=/opt/RMI/aix Thread model: aix gcc version 4.0.2 This may not be precise but it's the thread cleanup code in the destructor of APR. We were looking at making Log4CXX in a single threaded mode, but that proved very problematic, as we could not figure out how to set that up in the Ant build. We also were not clear if that was easily supported. -----Original Message----- From: Andreas Fester [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 12:26 PM To: Log4CXX User; Ron Ohmer Subject: Re: Core file on AIX Ron, which version of AIX are you using, and which compiler (gcc/visual age; which version)? Can you provide a minimal code example which causes the crash? Thanks, Andreas Ron Ohmer wrote: > During the destructor phase of Log4CXX we are experiencing core files > being dropped. This happens every time, and we know it is in the > destructor. > > Does anyone else run Log4-0.9.8 on AIX and see this issue? We only see > it on AIX and everything "works" fine, except the core at the end. > > Ron