[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev memory leaks vs corruption
From: |
pg |
Subject: |
Re: lynx-dev memory leaks vs corruption |
Date: |
Fri, 4 Dec 1998 10:26:34 -0700 (MST) |
In a recent note, Larry W. Virden said:
> Date: Thu, 3 Dec 1998 23:03:26 -0500 (EST)
>
> memory leak
> The result of allocating memory (ala calloc/malloc/etc.) but not
> free-ing the memory after finishing it's use.
>
> memory corruption
> The result of writing more data out than is available - for instance
> writing 30 bytes of data into a 20 byte long array...
> --
I would also count as "memory corruption" the result of free-ing the
same pointer value more than once.
-- gil
- Re: lynx-dev 2-8-1 bug: further (2), (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 <=
- 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, 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