This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [1.7] Backslash incorrectly triggers DOS style path warning
On Wed, Apr 22, 2009 at 02:31:02PM -0400, Christopher Faylor wrote:
>On Wed, Apr 22, 2009 at 07:08:26PM +0200, Corinna Vinschen wrote:
>>On Apr 22 12:59, Christopher Faylor wrote:
>>> On Wed, Apr 22, 2009 at 06:49:44AM -0600, Eric Blake wrote:
>>> >> In other words, strace is mistakenly performing glob expansion on the
>>> >> subsidiary arguments to the program being traced, when we really wanted to
>>> >> trace ls with a literal argument of "*".
>>> >
>>> >And this strace limitation (bug?) was just a red herring.
>>>
>>> strace doesn't do glob expansion. Cygwin does glob expansion when it is
>>> run by a non-cygwin application. That is more-or-less what strace is.
>>> There is no easy way around this.
>>
>>`set CYGWIN=noglob' should help, shouldn't it?
>
>Hmm. Yes. Good idea. I guess strace itself could set that under the
>theory that any command line arguments it has received should not be
>glob expanded.
>
>I'll check in a fix for that.
Hmm. This would mean that you can't debug glob/noglob using strace
though... I guess I'll check in a fix for the common case where you
don't want to be surprised by having your quoted wildcards expanded.
The other case is probably only useful for cygwin DLL developers. I'm
sure that if this is a problem I'll hear a loud outcry from that massive
community.
cgf
--
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/