Re: [xml] Segfault in xmlDocDumpMemory with efence

Daniel Veillard wrote:

 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,
I believe Electric fence's malloc doesnt use fenceposts like the libc's malloc, so I doubt this is the issue. Each allocation gets its own page surrounded by two unmapped pages, so it is impossible to walk
to any other allocated memory without hitting an unmapped page first.

I can't use valgrind on this code because it doesnt support the needed system calls yet.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]