Was being fooled before because the newly malloc'd block had the same address as the previously freed block.vmware
parent
191d78948b
commit
a66f9e9292
Loading…
Reference in new issue