3.0.x HEAD crashing

Phil Mayers p.mayers at imperial.ac.uk
Wed Jun 18 16:23:00 CEST 2014

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(

More information about the Freeradius-Devel mailing list