[xmlsec] memory corruption detected by libxml2 memory debugs

Daniel Veillard veillard at redhat.com
Thu Nov 25 05:32:19 PST 2004


On Thu, Nov 25, 2004 at 01:50:40PM +0100, Tomas Sieger wrote:
> I've tracked down the "xmlMemFree" problem:
> 
> #0  xmlMallocBreakpoint () at xmlmemory.c:145
> #1  0xf6f03b05 in xmlMemFree__internal_alias (ptr=0xf6f848cb) at 
> xmlmemory.c:459
> #2  0xf6fc100c in xmlSecCryptoDLFree (ptr=0x1a) at ../../src/dl.c:316
> #3  0xf6fb8dad in xmlsec_lt_dlexit () at ../../src/xmlsec-ltdl.c:1418
> #4  0xf6fc10e8 in xmlSecCryptoDLShutdown () at ../../src/dl.c:374
> #5  0xf6fdedf0 in xmlSecShutdown () at ../../src/xmlsec.c:113
> #6  0x08048d9f in main (argc=3, argv=0xfef8eeb4) at sign1.c:107

  Smells like a block freed with xmlFree() but not allocated by 
xmlMalloc() or xmlRealloc().

Daniel

-- 
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
veillard at redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/



More information about the xmlsec mailing list