Re: [xml] Segfault in xmlDocDumpMemory with efence

[Daniel Veillard <veillard redhat com>]

On Thu, Feb 19, 2004 at 02:30:52PM -0800, Dirk Morris wrote:
> I get a segfault in xmlDocDumpMemory when using electric fence.
> (linux 2.6.2)
[...]
> (gdb) where
> #0  0x4010b5df in memalign () from /usr/lib/libefence.so.0
> #1  0x4010bc4d in malloc () from /usr/lib/libefence.so.0
> #2  0x4005f635 in xmlBufferCreate () from /usr/lib/libxml2.so.2
[..]
> Any ideas what is happening?
> Without efence, everything works as expected, but I like to use it for 
> developement.
> Let me know if anymore information would be useful.

  Crash in malloc in Linux are usually due to a corrupted
memory allocator data structure. Use valgrind with your code it
offers a far more systematic check than efence,

Daniel

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