Guten Tag Andreas Volz,
am Dienstag, 18. Januar 2011 um 00:15 schrieben Sie:
Program received signal SIGSEGV, Segmentation fault.
0x001b2614 in ~ObjectPtrT (this=0x80ef7b8, __in_chrg=value optimized out)
at /usr/include/log4cxx/helpers/objectptr.h:100
100
I had the same problem. In my case, It was caused because log4cxx uses APR
libraries, and in my project I was using too. Are you using APR in your
project? are you making a apr_terminate in your code?
Regards
2011/1/18 Thorsten Schöning tschoen...@am-soft.de
Guten Tag Andreas Volz,
am
I have the same problem if I use log4cxx.AsyncAppender.
I fixed the problem by calling log4cxx::LogManager::shutdown(); before the
end of the process.
It's not very clean but it works.
On Tue, Jan 18, 2011 at 09:40, Oscar Pernas os...@pernas.es wrote:
I had the same problem. In my case, It was
I resolved it not calling the apr_terminate method. Log4cxx call it when the
destructor is called.
2011/1/18 Fabian Jacquet fabian.jacq...@gmail.com
I have the same problem if I use log4cxx.AsyncAppender.
I fixed the problem by calling log4cxx::LogManager::shutdown(); before the
end of the
When I said he called a 'aprterminate ()' wanted to _not_ called
'aprterminate ()', which had commented on log4cxx
thanks
Quoting Thorsten Schöning tschoen...@am-soft.de:
Guten Tag carlos_jime...@encopim.com,
am Dienstag, 18. Januar 2011 um 13:47 schrieben Sie:
Anyone have any idea?
