X-Recipient:	archive-cygwin AT delorie DOT 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=UeQl/LGGT4PFCDY+
	MvtU8QgwsKlX/WBvlx723ze6cDNnW3hZINGGUc4e3Ve2oIyeIUsO7GND0b8j8evp
	dLpJSt9+zu9dyK+FKbmkWUmIiGiHaQHRcKdXnygfwJYF4Fc5Hp1HknhWaxk+EFBm
	s6XBkCux9/29AcATrMqN41qB2/w=
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=DmnBHI9Xr6FD1LBZkMMkeu
	nKs5w=; b=QwocSiRZzmLV72ukf6MsxVyFvVzQFcvpr6cR5NGBQc0kIhHws+iH9n
	Z1YjbPM3BEaLmc545dnQrzszAX4bKCqsQ24lLl/zGM9uaPSNAGvdw/tp+NN17X42
	u49LSZ5iC2YHEedNUUQC/nGGEdn4xujJDLiVqOvy8G22kTTv3RGvE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.7 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*Ad:D*tv, downloaded, bizarre, Hx-languages-length:1052
X-HELO:	mga04.intel.com
X-ExtLoop1:	1
From:	"Soegtrop, Michael" <michael DOT soegtrop AT intel DOT com>
To:	Wouter van Doorn <wouter AT vandoorn DOT tv>,
	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	RE: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
Date:	Thu, 22 Jun 2017 17:46:21 +0000
Message-ID:	<0F7D3B1B3C4B894D824F5B822E3E5A175B275C65@IRSMSX102.ger.corp.intel.com>
References:	<CANZ2p_ckjzWEp0uPoJ8MAXh=0B6ZhWQVt9v_NmsFP-fpoX-sEg AT mail DOT gmail DOT com> <oiepk2$78o$1 AT blaine DOT gmane DOT org> <CANZ2p_cpjbjvZfOgSKAmsCT92QHC1i-yPc2BosJgL6u4LCdypQ AT mail DOT gmail DOT com> <oigj20$2ot$1 AT blaine DOT gmane DOT org> <CANZ2p_dgYfAemU55ssSUkJdnX4ALEAFcWtw+h9R_vM4Z-VYzaw AT mail DOT gmail DOT com>
In-Reply-To:	<CANZ2p_dgYfAemU55ssSUkJdnX4ALEAFcWtw+h9R_vM4Z-VYzaw@mail.gmail.com>
dlp-product:	dlpe-windows
dlp-version:	10.0.102.7
dlp-reaction:	no-action
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id v5MHm0Rj024174

Dear Wouter,

when things get bizarre on Windows, I tend to use Sysinternals/Microsoft ProcMon. It is free and can be downloaded here:

https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx

ProcMon shows you all Windows system calls with parameters and error results. You should see the CreatProcess call and possibly can see why it fails. Since Cygwin in the end creates a windows process with windows system calls, it should also help for Cygwin. In case your process does start and fails during initialization, you can also see the Windows system calls it does. If there are DLLs missing, you can also see that.

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

- Raw text -