GNU bug report logs - #6784
24.0.50; cmdproxy incosistency with command pathnames

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Laimonas Vėbra <laimonas.vebra <at> gmail.com>
Cc: 6784 <at> debbugs.gnu.org
Subject: bug#6784: 24.0.50; cmdproxy incosistency with command pathnames
Date: Wed, 04 Aug 2010 06:08:25 +0300

> Date: Tue, 03 Aug 2010 23:57:16 +0300
> From: Laimonas Vėbra <laimonas.vebra <at> gmail.com>
> CC: 6784 <at> debbugs.gnu.org
> 
> Laimonas Vėbra wrote:
> 
> > I guess, that CreateProcess(), in this case, internally processes
> > command line args, i.e. program names/paths ('c:/cygwin/bin/ls',
> > 'grep'), that it passes to cmd.exe and because command name/path is not
> > correctly/appropriately constructed (should be backslashed), it (chain
> > CreateProcess()->cmd.exe) fails.
> 
> Wrong. Actually it's cmd.exe that fails if command string contains pipe 
> and (subsequent slashed, not backslashed) program names are not quoted.
> 
> Works:
> cmd.exe /c c:/cygwin/bin/ls | grep foo
> cmd.exe /c c:/cygwin/bin/ls | C:\cygwin\bin\grep foo
> cmd.exe /c c:/cygwin/bin/ls | "C:/cygwin/bin/grep" foo
> cmd.exe /c "c:/cygwin/bin/ls" | "C:/cygwin/bin/grep" foo
> 
> Fails:
> cmd.exe /c c:/cygwin/bin/ls | C:/cygwin/bin/grep foo

In the case in point, the problem was with the executable _before_
the pipe.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.