X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <488609E0.5F425C4B@dessent.net>
Date: Tue, 22 Jul 2008 09:25:04 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.0-19: Still unexplained path problems
References: <6086F48CE8E1479DB51E00035DFD5B14 AT cit DOT wayne DOT edu> <20080722094517 DOT GF5251 AT calimero DOT vinschen DOT de> <4885CCBE DOT 8090305 AT byu DOT net> <20080722135643 DOT GA21785 AT calimero DOT vinschen DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Corinna Vinschen wrote:

> Can you create an strace of a testcase (building git or something)
> which shows where and how the paths are generated?  Maybe we can
> workaround this in Cygwin itself by tweaking paths missing a / or \
> after the colon...

Here's a testcase:

$ cat >tc.c <<EOF
#include <windows.h>
#include <stdio.h>

int main()
{
  char buf[512];
  
  GetModuleFileName (NULL, buf, sizeof (buf));
  puts (buf);
  return 0;
}
EOF

$ gcc -mno-cygwin tc.c

$ ./a
\\?\C:\cygwin\home\brian\testcases\native-argv0\a.exe

You can also reproduce this just by running "tclsh".  The problem is
that tcl is a native app and uses the w32api directly, and so these
native paths leak into it and it's un-equipped to use them properly.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/