18 Jun
2014
18 Jun
'14
10:23 a.m.
On 18/06/14 13:55, Phil Mayers wrote:
I didn't get a talloc report (or a valid core, grr valgrind!) but it
Never mind, the talloc report is of course not expected (or useful if the heap is corrupted) Caught another one under gdb; again looks like heap corruption, but digging around in glibc internals is not proving fruitful in terms of finding what was written into the RAM, since the failure happens much later when not running under valgrind :o(