Subject: Re: Possible bug relating to malloc()/realloc(), popen(), and read()
To: None <port-i386@NetBSD.org>
From: J Chapman Flack <flack@cs.purdue.edu>
List: port-i386
Date: 12/08/2004 12:49:13
Michael Graff wrote:
> Note the "possibly moved" part.
> realloc() does not guarantee that the new pointer is the same as the old,
> only that the contents were copied if it was moved.

I think it was cleared up about a week ago that the poster understood that,
and had a somewhat different issue in mind.

-Chap