的libxml2：xmlNewTextWriterFilename泄漏

下面的代碼編譯正確的valgrind報告沒有泄漏：的libxml2：xmlNewTextWriterFilename泄漏

# include <libxml/encoding.h> 
# include <libxml/xmlwriter.h> 

int main(void) { 
    xmlTextWriterPtr XMLWriter = xmlNewTextWriterFilename("example.xml", 0); 
    xmlTextWriterStartDocument(XMLWriter, NULL, NULL, NULL); 
    xmlTextWriterEndDocument(XMLWriter); 
    xmlFreeTextWriter(XMLWriter); 
    xmlCleanupParser(); 
    return 0; 
} 

----------------------------------------- 

==26059== HEAP SUMMARY: 
==26059==  in use at exit: 0 bytes in 0 blocks 
==26059== total heap usage: 16 allocs, 16 frees, 4,774 bytes allocated 
==26059== 
==26059== All heap blocks were freed -- no leaks are possible

一旦編碼在xmlNewTextWriterFilename調用指定的，但是，希拉里隨之而來：

# include <libxml/encoding.h> 
# include <libxml/xmlwriter.h> 

int main(void) { 
    xmlTextWriterPtr XMLWriter = xmlNewTextWriterFilename("example.xml", 0); 
    xmlTextWriterStartDocument(XMLWriter, NULL, "UTF-8", NULL); 
    xmlTextWriterEndDocument(XMLWriter); 
    xmlFreeTextWriter(XMLWriter); 
    xmlCleanupParser(); 
    return 0; 
} 

----------------------------------------- 

==26082== HEAP SUMMARY: 
==26082==  in use at exit: 422 bytes in 17 blocks 
==26082== total heap usage: 36 allocs, 19 frees, 9,224 bytes allocated 
==26082== 
==26082== 5 bytes in 1 blocks are still reachable in loss record 1 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x494942FF: ??? 
==26082== 
==26082== 6 bytes in 1 blocks are still reachable in loss record 2 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x37: ??? 
==26082== 
==26082== 6 bytes in 1 blocks are still reachable in loss record 3 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x39350048: ??? 
==26082== 
==26082== 7 bytes in 1 blocks are still reachable in loss record 4 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x45003630: ??? 
==26082== 
==26082== 9 bytes in 1 blocks are still reachable in loss record 5 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x454C3630: ??? 
==26082== 
==26082== 9 bytes in 1 blocks are still reachable in loss record 6 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x45423630: ??? 
==26082== 
==26082== 9 bytes in 1 blocks are still reachable in loss record 7 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x49494352: ??? 
==26082== 
==26082== 11 bytes in 1 blocks are still reachable in loss record 8 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x40EC23B: xmlStrndup (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x39353837: ??? 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 9 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EB28: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 10 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EB44: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 11 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EB6C: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 12 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EB94: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 13 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EBB6: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 14 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EBCC: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 15 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EBE2: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 20 bytes in 1 blocks are still reachable in loss record 16 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406E9D1: xmlNewCharEncodingHandler (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x406EC02: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== 200 bytes in 1 blocks are still reachable in loss record 17 of 17 
==26082== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==26082== by 0x406EABE: xmlInitCharEncodingHandlers (in /usr/lib/i386-linux-gnu/libxml2.so.2.7.8) 
==26082== by 0x41B54D2: (below main) (libc-start.c:226) 
==26082== 
==26082== LEAK SUMMARY: 
==26082== definitely lost: 0 bytes in 0 blocks 
==26082== indirectly lost: 0 bytes in 0 blocks 
==26082==  possibly lost: 0 bytes in 0 blocks 
==26082== still reachable: 422 bytes in 17 blocks 
==26082==   suppressed: 0 bytes in 0 blocks

什麼辦法呢？這是作業的東西 - 不能忽視valgrind的結果。

來源

2012-12-16 Witiko

在調用xmlCleanupParser（）之前添加對xmlCleanupCharEncodingHandlers()的調用。

在我的Mac OS 10.7.5開發機器（libxml 20703）上，這修復了libxml2中報告的「可到達」漏洞。

順便說一下，???意味着目標文件的調試符號不可用。它可以是非常有用有用的時候追查內存泄漏有這個信息。安裝調試信息的過程取決於Linux發行版。例如，在Ubuntu上，您可以使用sudo apt-get install libxml2-dbg安裝libxml2調試信息。見https://live.gnome.org/GettingTraces/DistroSpecificInstructions

來源

2012-12-16 18:20:49

謝謝，解決了它。我不能相信這種方法沒有列在libxml2網頁的「使用庫後清理」一節中。 – Witiko

似乎這是固定的，在libxml2中2.9.2'xmlCleanupParser（）'所做的第一件事是調用'xmlCleanupCharEncodingHandlers（）' –

的libxml2：xmlNewTextWriterFilename泄漏

回答

相關問題