Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsh!daw
From: daw@cbnewsh.att.com (David Wolverton)
Newsgroups: comp.lang.c
Subject: Realloc() considered unsafe (was Re: Safe coding practices)
Message-ID: <1991Jan25.180832.2528@cbnewsh.att.com>
Date: 25 Jan 91 18:08:32 GMT
References: <1991Jan24.060707.22566@tkou02.enet.dec.com> <22870@well.sf.ca.us> <22311:Jan2502:34:1191@kramden.acf.nyu.edu>
Distribution: usa
Organization: AT&T Bell Labs, Lincroft, NJ
Lines: 12

In article <22311:Jan2502:34:1191@kramden.acf.nyu.edu>, brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> [ lots deleted ]
> Now you can talk all you want about reallocating memory (btw, there's no
                                                                ^^^^^^^^^^
> safe way to use realloc(), but you knew that) ...
  ^^^^^^^^^^^^^^^^^^^^^^^^^

OK, I'll bite.  I didn't know that.  So, what is the problem
with realloc()?

Dave Wolverton
daw@attunix.att.com