Re: lynx-dev memory leaks vs corruption

[Larry W. Virden]

> how does that corrupt memory?
> surely, if it's been freed, it's not there to be freed again.

On some platforms freeing a pointer that's already been freed results in a
application crash.

Another memory corruption - making use of a pointer after it has been freed...


> (and thanx to LV for his enlightening reply)

I am glad that I can be of some service.  Sometimes I feel like I should
do more - however, I've more "irons in the fire" than I have time to manage.
-- 
Larry W. Virden                 <URL: mailto:address@hidden>
<URL: http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.