This is the mail archive of the
mailing list for the Cygwin project.
Re: batch script execution failing with 255 exit code in cygwin 1.7.28
- From: "Weber, Mark" <mark dot weber at dnvgl dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Thu, 20 Mar 2014 22:35:06 +0000
- Subject: Re: batch script execution failing with 255 exit code in cygwin 1.7.28
- Authentication-results: sourceware.org; auth=none
I am also having some trouble with the latest version of Cygwin, which includes
I am having a related issue, with C++ code that parses the command line.
The command line we support is something like -
program_name arg1 -option1=val1 -option2=val2 ...
You get the idea.
Now, with the above mentioned Cygwin patch, we are seeing the input arguments
arg1 "-option1=val1" "-option2=val2" ...
If this were the extent of the issue, it would be no big deal to
strip off the quotes. However, the user may have put quotes on the
command line himself, which Cygwin now moves around.
program_name arg1 -option1="file name with spaces in it"
With the patch, is there any way to reliably tell what the user entered
on the command line?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple