Re: FW: A bug in CYGWIN exec() and revision of argument values

2012-12-07 Thread Christopher Faylor
On Fri, Dec 07, 2012 at 01:33:52PM +, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: >Hi, > >Just checking whether this is going to be fixed, or should be keep >working around by passing the lowercased version of the "/C" switch ? > >> if (ac == 3 && argv[1][0] == '/' && argv[1][1] == 'c' && >>

FW: A bug in CYGWIN exec() and revision of argument values

2012-12-07 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C]
Hi, Just checking whether this is going to be fixed, or should be keep working around by passing the lowercased version of the "/C" switch ? > if (ac == 3 && argv[1][0] == '/' && argv[1][1] == 'c' && > (iscmd (argv[0], "command.com") || iscmd (argv[0], "cmd.exe"))) > Regards, Anton Lavr

A bug in CYGWIN exec() and revision of argument values

2012-11-29 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C]
Hi, I stumbled across yet another problem (or two), now in CYGWIN exec() implementation, which is demonstrated by the test case. 1. Using CMD.EXE as a command with the "/C" switch (note the capital letter just as Windows documents this switch for CMD.EXE) does not trigger the special hand