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/