[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 12:58:39 -0500 (EST) |
Re: freeing already freed pointers
I guess in some ways one would call memory corruption any use of memory
which results in crashes or incorrect behavior <grin>
For instance, another case that kind of falls into this area is passing
a pointer of a local variable to a calling program:
.
.
.
sub1(stuff);
:
:
int * sub1(int stuff)
{
int t;
return &t;
}
--
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: strace, (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 <=
- 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