[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev memory leaks vs corruption
|
From: |
Philip Webb |
|
Subject: |
Re: lynx-dev memory leaks vs corruption |
|
Date: |
Fri, 4 Dec 1998 21:22:01 -0500 (EST) |
981204 gil wrote:
> I would also count as "memory corruption"
> the result of freeing the same pointer value more than once.
how does that corrupt memory?
surely, if it's been freed, it's not there to be freed again.
(and thanx to LV for his enlightening reply)
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : address@hidden
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto
- 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 <=
- Re: lynx-dev memory leaks vs corruption, mattack, 1998/12/04
- Re: lynx-dev memory leaks vs corruption, Larry W. Virden, 1998/12/04
- 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