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: 30 Oct 2001 17:18:57 -0500
Message-ID: <20011030221857.2548.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin-developers AT cygwin DOT com
In-reply-to: <20011030185024.32684.qmail@lizard.curl.com> (message from
	Jonathan Kamens on 30 Oct 2001 13:50:24 -0500)
Subject: Re: New 1.3.4-blocking problem: execvp causes $0 to contain
   windows path instead of Unix path
References:  <20011030185024 DOT 32684 DOT qmail AT lizard DOT curl DOT com>

OK, this broke between 10/22 and 10/23.  It's almost certainly a
result of this change:

  date: 2001/10/22 16:40:26;  author: cgf;  state: Exp;  lines: +8 -0
  * libc/posix/execvp.c: Remove obsolete CYGWIN32 considerations throughout.
  * signal.h: Change comment to reflect __CYGWIN__ rather than __CYGWIN32__.
  * popen.c (popen): Use __CYGWIN_ rather than __CYGWIN32__.
  * system.c (_system_r): Ditto.

However, I can't see anything in this change that actually explains
why the bug would suddenly start happening.  I suspect that in fact
this change is correct but unmasked a previously existing bug.

I've got to leave in a few minutes.  I may or may not have time to
look at it more tonight; if not, I'll keep looking in the morning.

  jik