When I said he called a 'aprterminate ()' wanted to _not_ called
'aprterminate ()', which had commented on log4cxx
thanks
Quoting Thorsten Schöning :
Guten Tag carlos_jime...@encopim.com,
am Dienstag, 18. Januar 2011 um 13:47 schrieben Sie:
Anyone have any idea?
Don't call apr_terminate
Guten Tag carlos_jime...@encopim.com,
am Dienstag, 18. Januar 2011 um 13:47 schrieben Sie:
> Anyone have any idea?
Don't call apr_terminate at all, uncomment it in Log4cxx.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefo
I had a similar problem, after exit(0):
*** glibc detected *** ./main: double free or corruption (out): 0x08f10b20 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb7356624]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7358826]
/usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb75472e1]
/usr/local/lib
I resolved it not calling the apr_terminate method. Log4cxx call it when the
destructor is called.
2011/1/18 Fabian Jacquet
> 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
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 wrote:
> I had the same problem. In my case, It was caused because
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
> Guten Tag Andreas Volz,
> am Dienstag, 18. Januar 2011 u
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=)
> at /usr/include/log4cxx/helpers/objectptr.h:100
> 100 p->releaseRef();
Sounds th
Hello,
I just started with using log4cxx. It's a nice logging library and I
like using it. But for some reason I get a crash at exiting my program.
I run it in the debugger and here is the result:
Program received signal SIGSEGV, Segmentation fault.
0x001b2614 in ~ObjectPtrT (this=0x80ef7b8, __in
