X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:mime-version
	:content-transfer-encoding; q=dns; s=default; b=yrnt9dLv5s/7BGhZ
	GkcCCBlx6RI3naVbQHCh0mZEXpuyaatjsxFQkZbpCm/pTXItW2u9RiQJ8pZj70/0
	4V50AhiI3qB/I+/ujr8PZ68NoCW7gK2d33EEsG97Ye2FEm/t+Q7jqEPP8PzXJo9M
	knSnQPbkfQhNrQ49i/r1941rLZY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:mime-version
	:content-transfer-encoding; s=default; bh=JEXg14WyAz1FpRpU48x1LM
	WwTuk=; b=FRvv1ZamU5deqZ356bUaf9UeRXnLOrflXaiYV4XVAi3j6/7ZEvfnz0
	AJ7scV/Cg3UOz6Z412YrDRwZ9OzHIEGb8QDcDDdQUG+EpIM909cOfW5TaovJBbbu
	pxzqrWpqYqPQX6qIsAMG77kNXfASAIPFk+6xTa+2leQnavwuOuGoU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 spammy=HTo:D*tv, H*Ad:D*tv, boot, HX-Envelope-From:sk:michael
X-HELO: mga11.intel.com
X-ExtLoop1: 1
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Wouter van Doorn <wouter@vandoorn.tv>,
        "cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
Date: Tue, 27 Jun 2017 08:14:27 +0000
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A175B276ED1@IRSMSX102.ger.corp.intel.com>
References: <CANZ2p_ckjzWEp0uPoJ8MAXh=0B6ZhWQVt9v_NmsFP-fpoX-sEg@mail.gmail.com> <CANZ2p_ecq4LXNtWtShednD3n8efLkKOPujeiR9VtvboOsLOimA@mail.gmail.com> <CANZ2p_cgEkm9KSb-3YLbo=gvk8O+NB0dAsFn5TSw-zuY0tP5SQ@mail.gmail.com>
In-Reply-To: <CANZ2p_cgEkm9KSb-3YLbo=gvk8O+NB0dAsFn5TSw-zuY0tP5SQ@mail.gmail.com>
dlp-product: dlpe-windows
dlp-version: 10.0.102.7
dlp-reaction: no-action
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id v5R8F7gZ018044

Dear Wouter,

> One day on, and it's all reverted. Everything failing again in exactly the same way
> as before. It was too good to be true...

You might want to disassemble the good and bad binaries and compare the disassemblies. This should reveal what is going on. You can send me the binaries via private mail (as zip encrypted). Please note that the PATH has not only an influence at build time, but also at run time.

> I'll have to give up on cygwin, still appreciate the attempts at helping me.

You shouldn't. Of cause there is bogus SW which just isn't worth it, but Cygwin definitely doesn't fall into this category. 

One more advice: if computers behave erratically and don't have ECC memory, it is worthwhile to run a memory test (use memtest86, burn a boot CD and run it for 1 hour - don't trust in BIOS memory tests). I see broken memory about once or twice a year.

Best regards,

Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

--
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


