This is the mail archive of the
cygwin-developers@sources.redhat.com
mailing list for the Cygwin project.
Re: Anyone having problems with the latest winsup/cygwin1.dll?
- To: Cygwin Developers List <cygwin-developers at cygwin dot com>
- Subject: Re: Anyone having problems with the latest winsup/cygwin1.dll?
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Thu, 14 Dec 2000 18:39:57 -0500
- References: <FMEOJCMLNIMPBKAPFPIHCEKCCFAA.tailbert@yahoo.com>
- Reply-To: cygwin-developers at cygwin dot com
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