Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Chris Faylor Date: Fri, 13 Oct 2000 16:43:55 -0400 To: cygwin@sources.redhat.com Subject: Re: Two snapshot bugs Message-ID: <20001013164355.D1492@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <779F20BCCE5AD31186A50008C75D99791717B7@silldn_mail1.sanwaint.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <779F20BCCE5AD31186A50008C75D99791717B7@silldn_mail1.sanwaint.com>; from EFifer@sanwaint.com on Fri, Oct 13, 2000 at 04:13:12PM +0100 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 cygwin-unsubscribe@sourceware.cygnus.com