DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type; q=dns; s=default; b=F6yj1BpcIlBFW4WX
	Ezut/e1HGb4Wkg8RiH+0GKf4xhh1yCW8fDTlIq9KPT9FRNilEzrqnBYRMM2fmQP+
	1lbvPUizOuW5+lE2sZgYAfsNGHEzb47lHvdJ2RT9Bl76YhO7igH3vYMQ9WZO0YHs
	JjFyK+AFbXu0OKYCUZ4GhYpQQ+E=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: Problem with latest setup-x86.exe
Date: Mon, 18 Nov 2013 20:29:44 +0100
Lines: 20
Message-ID: <87mwl1y0d3.fsf@Rainer.invalid>
References: <528A5578.3070005@w5pny.com>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Harry G McGavran Jr writes:
> int main(int argc, char **argv, char **envp)

The entry point in setup.exe is WinMain, which has a different signature
and entry point.  The use of __argv ties into the actual RTC entry point
of WinMainCRTStartup and gets populated on startup.  If indeed on one of
your machines the behaviour is different than on others, you might pick
up a different RTC.  Try to find out from where this CRT, more
specifically msvcrt.dll, is coming.  These days you can expect a dozen
of these in several places on your system and with the wrong path
settings you might pick up a rogue one.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


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