This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: New 1.3.4-blocking problem: execvp causes $0 to contain windows path instead of Unix path
- To: cygwin-developers at cygwin dot com
- Subject: Re: New 1.3.4-blocking problem: execvp causes $0 to contain windows path instead of Unix path
- From: Jonathan Kamens <jik at curl dot com>
- Date: 30 Oct 2001 17:18:57 -0500
- References: <20011030185024.32684.qmail@lizard.curl.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