BTW here is also the stack when one of the exceptions mentioned above is
thrown:
terminate called after throwing an instance of
'log4cxx::helpers::MutexException'
what(): Mutex exception: stat = 1
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x41401940 (LWP 18319)]
0x000000387c630265 in raise () from /lib64/libc.so.6
(gdb) where
#0 0x000000387c630265 in raise () from /lib64/libc.so.6
#1 0x000000387c631d10 in abort () from /lib64/libc.so.6
#2 0x00000038822becb4 in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib64/libstdc++.so.6
#3 0x00000038822bcdb6 in ?? () from /usr/lib64/libstdc++.so.6
#4 0x00000038822bcde3 in std::terminate() () from /usr/lib64/libstdc++.so.6
#5 0x00000038822bceca in __cxa_throw () from /usr/lib64/libstdc++.so.6
#6 0x00002aaaaafd3e9d in log4cxx::helpers::synchronized::~synchronized
(this=<value optimized out>,
__in_chrg=<value optimized out>) at synchronized.cpp:46
#7 0x00002aaaaaf7745c in log4cxx::Hierarchy::isDisabled (this=0x61bf40,
level=10000) at hierarchy.cpp:267
#8 0x00002aaaaaf8ca1f in log4cxx::Logger::isEnabledFor (this=0x61e080,
level1=...) at logger.cpp:287
#9 0x00002aaaaaf97079 in log4cxx::logstream_base::logstream_base
(this=0x61bd08, log=<value optimized out>, lvl=...)
at logstream.cpp:47
#10 0x00002aaaaaf97379 in log4cxx::logstream::logstream (this=0x478b,
logger=..., level=...) at logstream.cpp:181
#11 0x0000000000402d2e in myLog::myLog (this=0x61bd08) at mylog.cpp:12
There might be several things going wrong since the behavior differs between
the different throws and the segmentation fault.
--
View this message in context:
http://old.nabble.com/log4cxx-0.10.0%3A-Fix-for-64-bit-only-thread-safety-bug-in-ObjectPtrBase-tp21504865p29167958.html
Sent from the Log4cxx - Dev mailing list archive at Nabble.com.
