Summary: | memory leak in libxml2 2.6.22 [maybe others] (according to valgrind) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cody <met> |
Component: | [OLD] Development | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
code that demonstrates the problem
file I passed to the program ... |
Description
Cody
2005-11-10 12:25:47 UTC
Created attachment 72591 [details]
code that demonstrates the problem
I compiled this with:
gcc -Wall -g -ggdb3 -o valtest valtest.c -I/usr/include/libxml2 -lxml2
Then ran it with:
valgrind ./valtest test.xml
Created attachment 72592 [details]
file I passed to the program ...
Calling xmlCleanupParser after xmlFreeDoc makes valgrind stop complaining here. Sounds like a bug in the test program? If not, re-open. (In reply to comment #4) > Sounds like a bug in the test program? If not, re-open. I suppose it could be marked closed then. Tested and all is good with that function. Not sure why I didn't notice this before though (I could have sworn it never did this in the past). Is this new or did it do it before and I was blind ? Thanks though. Works for me. |