I resolved it not calling the apr_terminate method. Log4cxx call it when the destructor is called.
2011/1/18 Fabian Jacquet <[email protected]> > 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 <[email protected]> wrote: > >> 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 <[email protected]> >> >> 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 p->releaseRef(); >>> >>> Sounds that the following may be the reason: >>> >>> >>> http://mail-archives.apache.org/mod_mbox/logging-log4cxx-dev/200901.mbox/%[email protected]%3E >>> http://www.mail-archive.com/[email protected]/msg03188.html >>> >>> Mit freundlichen Grüßen, >>> >>> Thorsten Schöning >>> >>> -- >>> Thorsten Schöning >>> AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig >>> >>> Telefon: Potsdam: 0331-743881-0 >>> E-Mail: [email protected] >>> Web: http://www.am-soft.de >>> >>> AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam >>> Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow >>> >>> >> >> >> -- >> Óscar Pernas Plaza. >> > > -- Óscar Pernas Plaza.
