On 25/08/2014 11:33, Iñigo Martínez wrote:
Hi,
I have been looking at the memory usage of my programs using libxml2 y
using valgrind, and I have seen these messages:
==22134== Invalid read of size 8
==22134==at 0x519482F: xmlFreeNode (in
/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1)
Chris Johnson wrote:
xmlNewGlobalState() is not available to break in
It has probably been inlined by the compiler.
xmlOnceInit() is never called therefore pthread_key_create is never
called from xmlOnceInit().
I believe that we have found the problem. According to the following
URL you
Bjorn Reese wrote:
Chris Johnson wrote:
xmlNewGlobalState() is not available to break in
It has probably been inlined by the compiler.
xmlOnceInit() is never called therefore pthread_key_create is never
called from xmlOnceInit().
I believe that we have found the problem. According to
On Fri, Aug 11, 2006 at 07:38:22AM -0400, Chris Johnson wrote:
Bjorn Reese wrote:
Chris Johnson wrote:
xmlNewGlobalState() is not available to break in
It has probably been inlined by the compiler.
xmlOnceInit() is never called therefore pthread_key_create is never
called from
Chris Johnson wrote:
Thanks for the reply. I've done further testing and found some very
interesting results as follows. It turns out when I compile and link
parse3.c with static version of libxml purify turns up several memory
leaks as shown in the attached a.out.static. Thinking the
Bjorn Reese wrote:
Chris Johnson wrote:
While working with parser3.c example
(http://xmlsoft.org/examples/parse3.c) on Solaris 8 Rational Purify
identifies several areas as having leaked memory.
Normally Purify reports how many bytes have been leaked and a stacktrace
of where the memory was
On Tue, Aug 08, 2006 at 09:04:20AM -0400, Chris Johnson wrote:
While working with parser3.c example
(http://xmlsoft.org/examples/parse3.c) on Solaris 8 Rational Purify
identifies several areas as having leaked memory.
Modifying parse3.c to
while(1)
example3Func(document, 6);
and
