From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) by sourceware.org (Postfix) with ESMTPS id 99D76383E814 for ; Thu, 11 Jun 2020 04:46:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 99D76383E814 Received: by mail-wr1-x42a.google.com with SMTP id q11so4669387wrp.3 for ; Wed, 10 Jun 2020 21:46:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fX4IIBSNfphFyz1ij0fnrBEEjyIc0sNGE8YJhd+E4NI=; b=EvCXQi7BIn/WKS4gZORM4FfJSmmIFX8+T88tsgQMOVeZ2YZmPcVIMTVX97+K3aoQzu ypbHvlVfvBKppqAyJqHmbTt+/6QMuNSqtTnTmrv9bF46xgHSr2Nyh50mG28FoeajCLPA 81jFnfLa34gt/WNe4e6BJaGIpJICTrLBLhxt/b35YkaDOARSDzyh3Vz2LToF9Py7O50d +Wh+aNLu8q1GkHx+iZEkztUXGgmQA7Lq2VGyOavfMKISM/xmKpD8igwcCP0HSgmnnAzV eb+k7m2sBXTy/KZr28DHajObUUCu+frVI6+4yK8wiA9epE9JEU4mE2q8brJA+I8PA09a huFA== X-Gm-Message-State: AOAM530Alc4ZLfZ+Tyyhz137ZKA9WDAKa0fcXnJJK/bZz+qzW3YRqDbD OHeWOyuxk/hakRDPeEUtkP3UIIb2pxs= X-Google-Smtp-Source: ABdhPJzuerZpTxBww32SVvAuxCewcC/OJun77qIar3u+TzTBnFChzn+rthzqw3IoyICng+uYnBZ3cw== X-Received: by 2002:adf:b60b:: with SMTP id f11mr7256312wre.7.1591850813242; Wed, 10 Jun 2020 21:46:53 -0700 (PDT) Received: from ?IPv6:2003:cc:9f3b:4cdf:d10:2b69:93c3:b229? (p200300cc9f3b4cdf0d102b6993c3b229.dip0.t-ipconnect.de. [2003:cc:9f3b:4cdf:d10:2b69:93c3:b229]) by smtp.gmail.com with ESMTPSA id a1sm2182765wmj.29.2020.06.10.21.46.52 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Jun 2020 21:46:52 -0700 (PDT) Subject: Re: [bug?] Spawning cygwin32 program from cygwin64 messes up backslashes To: cygwin@cygwin.com References: From: Marco Atzeri Message-ID: <1d3efe20-fa56-52c2-788c-df9b1502304f@gmail.com> Date: Thu, 11 Jun 2020 06:46:52 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: it Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2020 04:46:55 -0000 On 11.06.2020 03:05, Mingye Wang via Cygwin wrote: > Hi, > > The following test case script fails under cygwin64: > > ``` > out32=$(/cygdrive/c/cygwin/bin/echo.exe 'a\\ b') > out64=$(/cygdrive/c/cygwin64/bin/echo.exe 'a\ b') > test "$out32" = "$out64" > ``` > > In other words, while the correct (by-argv-memory) result is `a\\ b`, > cygwin32 gives `a\ b` as output instead. The test case works fine when > CYGWIN=noglob is set, but then `echo.exe 'a\" b'` fails miserably. > I miss to see why running a 32bit Cygwin from a 64 bit instance makes any sense and it will be worth to spend any time on handling this borderline case .