Hi,
First off, let me say that we've been using log4cxx for some years now
with great success. Its a wonderful library that really helps with
debugging and supporting code. Ive been using the log4cxx 0.10.0, but
upgraded to the svn trunk (r1755031) last week after having issues with
SocketHub
Guten Tag Peter Westman,
am Dienstag, 25. Oktober 2016 um 13:51 schrieben Sie:
> I get tons of valgrind errors (112 to be exact)[...]
I don't know valgrind very well, so what kind of errors are you
talking about? If it's resource leaks, some of those are known and
accepted to fix problems with mu
Yes, its resource leaks. The 122 errors was from another logging.xml
then the one supplied in my example (it had an async appender in root,
with a file and console appender under it), with the example I sent it
is actually 22 errors (see below). The invalid free is most likely
something to do w
Guten Tag Peter Westman,
am Dienstag, 25. Oktober 2016 um 14:40 schrieben Sie:
> Yes, its resource leaks.
Most of the leaks seem to have to do with levels, which were changed
by me because of problems in multi threading apps as well. Have a look
at the following bugs and try again with a reverted
Reverting 1566655 solved the problems. I'd prefer not to have to tinker
with reverting/patching when building. Do you mind if I work on a
solution for this and post it in LOGCXX-458 if I manage to create one?
/Peter
On 10/25/2016 06:49 PM, Thorsten Schöning wrote:
Guten Tag Peter Westman,
am
