On Fri, Oct 13, 2000 at 04:13:12PM +0100, Fifer, Eric wrote: > >I found something that changed from 1.1.4 to 1.1.5s (Oct-10). > >In some old code I had been careful to free memory from environment >variables that were unset, but now the free() triggers a SEGV. >Is this a bug or should I be doing something differently? environment variables are not guaranteed to have been allocated with malloc. This is consistent with UNIX, AFAIK. It was a deliberate change in cygwin. There should be a ChangeLog entry for this. cgf -- Want to unsubscribe from this list? Send a message to [EMAIL PROTECTED]
