Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Thu, 14 Dec 2000 18:39:57 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	Cygwin Developers List <cygwin-developers AT cygwin DOT com>
Subject:	Re: Anyone having problems with the latest winsup/cygwin1.dll?
Message-ID:	<20001214183957.B20516@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	Cygwin Developers List <cygwin-developers AT cygwin DOT com>
References:	<FMEOJCMLNIMPBKAPFPIHCEKCCFAA DOT tailbert AT yahoo DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<FMEOJCMLNIMPBKAPFPIHCEKCCFAA.tailbert@yahoo.com>; from tailbert@yahoo.com on Thu, Dec 14, 2000 at 05:31:12PM -0500

On Thu, Dec 14, 2000 at 05:31:12PM -0500, edward wrote:
>Hi CygPeeps,
>
>I'm having memory problems with the latest cygwin1.dll. I did a clean cvs co
>winsup today at around 1pm.
>
>The problem occurs at line 618 of environ.cc (version 1.38)
>
>before that line,
>
>eq = 0xA010209
>
>and after that line
>
>eq = 0x6100B622
>
>The crash always happens there, but it depends on which environment
>variables are set. In every case so far, line 617 never had to be executed,
>so it goes from line 616 to 618 then 619. The crash happens because eq is
>garbage by line 619. I suspect it's a memory problem because several
>iterations of this particular code works OK. Anyone happen to have purify on
>nt?
>
>Cheers,
>edward.
>
>    615       char *eq;
>    616       if ((eq = strchr (newp, '=')) == NULL)
>    617         eq = strchr (newp, '\0');
>    618       if (!myself->ppid_handle)
>    619         ucenv (newp, eq);

Since this happens very early in the initialization phase and no other
threads are running, it should be pretty easy to figure out what's
happening.  Single step until you see it happen...

cgf

- Raw text -