Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3CA9F97A.9EC8B967@yahoo.com>
Date: Tue, 02 Apr 2002 13:33:30 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: Earnie Boyd <Cygwin-Developers AT cygwin DOT com>
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: newlib/libc/stdlib/mallocr.c
References: <3CA9A7A9 DOT 1A8AD3C5 AT yahoo DOT com> <20020402151655 DOT GB17969 AT redhat DOT com> <3CA9CD1B DOT CC324CF3 AT yahoo DOT com> <20020402183141 DOT GA24930 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:
> 
> >
> >I would get segmentation faults within mallocr.c.  The first time it
> >occurred was the originating call was within the code I was adding.  I
> >modified the code a bit and that caused the malloc's in environ.cc to
> >issue the segmentation faults in mallocr.c.  If you need to know exactly
> >where in mallocr.c that was causing the problem I can most likely
> >reproduce it to get the failure point.
> 
> SEGVs are invariably a sign of attempts to free memory that hasn't been
> allocated.
> 

I wasn't freeing memory I was mallocing memory.  Once I've finished my
annual disk cleaning job I'll try to reproduce the problem.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com