Guten Tag Bonneau, Guy,
am Montag, 22. Mai 2017 um 21:02 schrieben Sie:
> Hierarchy::~Hierarchy(){
>
> delete loggers;
> delete provisionNodes;}
A workaround is applied to current trunk for this problem:
https://issues.apache.org/jira/browse/LOGCXX-430
Additionally have a look at the r
are shared pointer
> implemented by the library I would expect to nicely exit. Thus I am a little
> bit baffled at this point.
>
>
>
> From: Dave Birdsall
> Sent: Monday, May 22, 2017 2:48 PM
> To: Log4CXX User
>
> Subject: RE: log4
library I would expect to nicely exit. Thus I am a little
bit baffled at this point.
From: Dave Birdsall
Sent: Monday, May 22, 2017 2:48 PM
To: Log4CXX User
Subject: RE: log4cxx crashes on application exit
Hi,
Looking at your stack more carefully, it looks like the
things. Perhaps
there is a way to clean out the Hierarchy object first so that there is nothing
for it to destroy?
Dave
From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
Sent: Monday, May 22, 2017 11:43 AM
To: Log4CXX User
Subject: RE: log4cxx crashes on application exit
I am not a log4cxx
@logging.apache.org
Subject: log4cxx crashes on application exit
We have used log4cxx V0_10_0 since a few years with both Linux and Windows
without any issues until now. We have a setup to compile and build the log4cxx
shared library on both Linux and Window. We made a solution (sln) that can
build with
We have used log4cxx V0_10_0 since a few years with both Linux and Windows
without any issues until now. We have a setup to compile and build the log4cxx
shared library on both Linux and Window. We made a solution (sln) that can
build with Microsoft VS 2008 up to VS 2013. Our log4cxx is build un
