[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev memory leaks vs corruption
From: |
Larry W. Virden |
Subject: |
Re: lynx-dev memory leaks vs corruption |
Date: |
Fri, 4 Dec 1998 21:41:10 -0500 (EST) |
> 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.
- Re: lynx-dev 2-8-1 bug: print vs partial, (continued)
Re: lynx-dev 2-8-1 bug: print vs partial, Leonid Pauzner, 1998/12/03
lynx-dev memory leaks vs corruption, Philip Webb, 1998/12/03
- Re: lynx-dev memory leaks vs corruption, Larry W. Virden, 1998/12/03
- Re: lynx-dev memory leaks vs corruption, pg, 1998/12/04
- Re: lynx-dev memory leaks vs corruption, Larry W. Virden, 1998/12/04
- Re: lynx-dev memory leaks vs corruption, Philip Webb, 1998/12/04
- Re: lynx-dev memory leaks vs corruption, mattack, 1998/12/04
- Re: lynx-dev memory leaks vs corruption,
Larry W. Virden <=
- Re: lynx-dev memory leaks vs corruption, David Woolley, 1998/12/07
Re: lynx-dev 2-8-1 bug: print vs partial, Philip Webb, 1998/12/03
Re: lynx-dev 2-8-1 bug: print vs partial, Philip Webb, 1998/12/04
Re: lynx-dev 2-8-1 bug: print vs partial, dickey, 1998/12/03
Re: lynx-dev 2-8-1 bug: print vs partial, dickey, 1998/12/03
Re: lynx-dev 2-8-1 bug: print vs partial, dickey, 1998/12/03