Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On Fri, Feb 19, 2010 at 2:41 PM, Eric Blake wrote: > I haven't followed your queries closely (since you keep replying to > yourself). But it all boils down to: See here for the introduction to the problem: http://cygwin.com/ml/cygwin/2010-02/msg00464.html > what shell are you using, with its pa

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

According to Piotr Krukowiecki on 2/19/2010 5:52 AM: > '\' is an escape character in C, Unix, and Linux. In Windows, it's a > path separator. Use '/' instead when working with Cygwin and you'll > avoid allot of problems. Better yet, use POSIX paths exclusively. > [...] >> I don't kno

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On Fri, Feb 19, 2010 at 1:37 PM, Piotr Krukowiecki wrote: > On Thu, Feb 18, 2010 at 9:45 PM, Larry Hall (Cygwin) wrote: >> On 02/18/2010 03:24 PM, Piotr Krukowiecki wrote: >>> On Thu, Feb 18, 2010 at 7:02 PM, Larry Hall (Cygwin) On 02/18/2010 12:55 PM, Piotr Krukowiecki wrote: > - if the e

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On Fri, Feb 19, 2010 at 1:37 PM, Piotr Krukowiecki wrote: >>> "\\hostname" is remote path location, I don't think I can use >>> "//hostname" instead, either for cygwin program and especially not for >>> not-cygwin program, can I? (can't check it now) >> >> With Windows, you're free to use either pa

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On Thu, Feb 18, 2010 at 9:45 PM, Larry Hall (Cygwin) wrote: > On 02/18/2010 03:24 PM, Piotr Krukowiecki wrote: >> On Thu, Feb 18, 2010 at 7:02 PM, Larry Hall (Cygwin) >>> On 02/18/2010 12:55 PM, Piotr Krukowiecki wrote: - if the executed program is compiled with cygwin's gcc the program r

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

> Thanks to your createprocess.c/dumpargs.c pair, I could figure the existing > Cygwin's parsing without looking into its source code. It turned to ignore > the > escaping power of a bare (unquoted) backslash when it was followed by a > double > quote, which is against both MSVC and Bash

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

> As you can see dumpargs_gcc receives "\127.0.0.127\foo.cxx" and dumpargs_cl > receives "\\127.0.0.127\foo.cxx". Interesting. I am confused, too. (1) Native-only parameter passing: execv(PROG, ARGV) -> MSVCRT -> line = M(ARGV) -> CreateProcess( PROG, line, .. ) -> MSVC

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On 02/18/2010 03:24 PM, Piotr Krukowiecki wrote: On Thu, Feb 18, 2010 at 7:02 PM, Larry Hall (Cygwin) reply-to-list-only-lh at cygwin period com wrote: ^^ . Don't feed the spammers. Thanks. On 02/18/2010 12:55 PM, Piotr

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On Feb 18 21:24, Piotr Krukowiecki wrote: > On Thu, Feb 18, 2010 at 7:02 PM, Larry Hall (Cygwin) > wrote: > > On 02/18/2010 12:55 PM, Piotr Krukowiecki wrote: > >> - if the executed program is compiled with cygwin's gcc the program > >> receives \127.0.0.127\foo.cxx (just one backslash at the begi

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On Thu, Feb 18, 2010 at 7:02 PM, Larry Hall (Cygwin) wrote: > On 02/18/2010 12:55 PM, Piotr Krukowiecki wrote: >> - if the executed program is compiled with cygwin's gcc the program >> receives \127.0.0.127\foo.cxx (just one backslash at the begining). >> - if it's compiled with cl it gets \\127.0

Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

On 02/18/2010 12:55 PM, Piotr Krukowiecki wrote: Hello, In short, I have a problem with passing "\\127.0.0.127\foo.cxx" argument to a called program: - if the executed program is compiled with cygwin's gcc the program receives \127.0.0.127\foo.cxx (just one backslash at the begining). - if it's

CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)?

Hello, In short, I have a problem with passing "\\127.0.0.127\foo.cxx" argument to a called program: - if the executed program is compiled with cygwin's gcc the program receives \127.0.0.127\foo.cxx (just one backslash at the begining). - if it's compiled with cl it gets \\127.0.0.127\foo.cxx (do