Re: (ITS#3914) test030-relay frees already-freed memory

[ando@sys-net.it]

Howard Chu wrote:

> Might want to try again with ElectricFence, or see if the other tools 
> have an option to retain freed memory on a separate list (and delay 
> it) before making it available for re-use.

|In fact, with valgrind, the problem disappears when a reasonably small 
value is used instead of the default 1000000 blocks for
--freelist-vol=<number>.  This is not a proof, but coupled to stepping 
in with gdb, which shows the memory being corrupted after free, and then 
back on the block after being returned by a subsequent malloc (despite 
having the same pointer)...

p.
|


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497