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:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=h5KnQ12aTtd6LuC2
	S7bz7nxV8wEVLxeNak1kIdOXLTYi8OqsUmLUXpZyz/11INojIteFlzQuHKAISF0F
	jNCcBfQwMt+Fl/N//DzCMDkK7pWUvOyZ2eOcSb81ZJyJ0XGg+GtV6NRmalZNGp+h
	pu2Ux1VAAVIFIjTTvDMT7YbL2Yg=
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:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=WHGmNzDK+hENZYReRluR+9
	EXdoc=; b=f/oP/L+eCi2KSYEKMTR6KcyNsU3J+7eJs1rwHllfj8Yv1yizkYM3Bx
	rJJNwPjtqH0PDPpwo+3jRKK+NPb38exmnYRkUEgJjMSVbJAFfgrYGoN4YblTqMVf
	KZQNebi8F/078u02J1nO47pkDc/3b8aghSRa6jzl56lCw9N3Sn3Dk=
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.6 required=5.0 tests=BAYES_50,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	p3plsmtpa06-10.prod.phx3.secureserver.net
Message-ID:	<52827878.4030501@w5pny.com>
Date:	Tue, 12 Nov 2013 11:50:32 -0700
From:	Harry G McGavran Jr <w5pny AT w5pny DOT com>
Reply-To:	w5pny AT w5pny DOT com
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem with latest setup-x86.exe
References:	<52826B3B DOT 8030909 AT w5pny DOT com>
In-Reply-To:	<52826B3B.8030909@w5pny.com>

>On 11/12/2013 10:54 AM, Harry G McGavran Jr wrote:
>> On only one of my Windows 7 machines the latest setup-x86.exe
>> works but always exits with an Access Violation.
>> 
>> So, I downloaded the source to setup and built it.
>> 
>> But in order to make the build work, I had to remove -Werror
>> from the Makefile and add a definition for ARRAYSIZE to main.cc.
>> 
>> The fix to the Access violation was to remove an extra "_" in
>> the code for the argv handling in main.cc
>> 

On Tue, 12 Nov 2013 13:31:31 -0500, Christopher Faylor wrote:
>I appreciate your looking at the source code but given what you changed,
>I don't understand how what you did would fix that.  If your changes
>were really necessary then something would have to be seriously wrong
>with mscvrt handling of argv strings.  That points to a problem on
>your system, not in the code.

Perhaps, but I would have no idea how to figure out problems with mscvrt.
I found the problem by just using gdb on the setup.exe built
without the __argv fix.  __argv was always a null pointer.
(Since __argv seems to be a definition, I always had to look
at the results of invoking __argv when using gdb).
When looking at how _argv was handled, it looked like that was
the thing to use, so when I tried that, the pointers were all fine.
So, if in fact the original code is correct, I don't know how to
find out what changed in mscvrt.  Previous versions of setup-x86
seem not to have this problem for some reason.




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