This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Command line processing in dcrt0.cc does not match Microsoft parsing rules
- From: "Stephen Provine via cygwin" <cygwin at cygwin dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>, "Brian dot Inglis at SystematicSw dot ab dot ca" <Brian dot Inglis at SystematicSw dot ab dot ca>
- Date: Tue, 3 Sep 2019 16:38:19 +0000
- Subject: RE: Command line processing in dcrt0.cc does not match Microsoft parsing rules
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aVpTtN1NWoMhSpoakipC81sqB/HpVFW3KMkkme8WRm4=; b=YLLb0/p7ozRkJfTY9ITy0HsspBWmCzBjJM5GslIlDEaMZTHnOIcbdpYqmjtfls7ZGCAyHKPXGEZO0KPNc6JYTm3oTYviNF8ckFJY9m/CKysMzbfIzzBGD1pP/kUY6OZNrlfOX9B+B7hUgq04rsL8PJm0B+z31AAjdspBZKjsums0VVSP0ZWYoRk76jK6gJUNS/sKo1wlUr/CRQZNpyiLm6DYmba/BkKk1gjiqujeyrAMOMExFhMMnjfxNKvrrm0CoPykkDGGmkhpPe9SRIir59x1SfN0CdkdNoLXsCNShnzw7XIotxrwrfJsFrQyGXXfXPEsDUS33h8Y39ykATfRDg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aObPabQ4TOi+ZJmlwah3Ih1rfD2fP1i/KCkPWSpILOlBeIM/MUFR2Mg68eQuPs6dI8PsymdlL/zcrRTnz9IKVcGgFuVH24UhyVaasfjBsrWIEGl9kmeIfbjrB24BJMVqY+28LGG2srN3fiSWPWjD+G/TW7WF5EJQJQOolJD1TmRsXkltLF3N2E8QDaghPpXXegFEIkcqWUBfasBWG5JJ6ICGjfOYdG9zbqfJXCaTjgCVHf4Tep8k6GrVeIbAjB15q2APila9Brsn6NHXkEQ9m/3/D4q5Gd15AS6RFl82+tHghvWhKR73J5mqpsEhFydz9p9D4kUOJm9IzziToxzvBA==
- References: <MWHPR21MB08452919F35B1B0C5F0EB4DCB9BD0@MWHPR21MB0845.namprd21.prod.outlook.com> <MWHPR21MB0845F78385792965A94E0CD9B9BD0@MWHPR21MB0845.namprd21.prod.outlook.com>
- Reply-to: Stephen Provine <stephpr at microsoft dot com>
On 2019-08-30 21:58, Brian Inglis wrote:
> Not being in the same Cygwin process group and lacking the appropriate interface
> info indicates that the invoker was not Cygwin.
Should I interpret this to mean the "winshell" parameter is not an accurate
statement of what I thought it was for and because there is no way to reliably
determine if the calling process was from Cygwin or not, behavior like I suggest
is actually impossible?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple