DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ykCa7662UCVqYlWp
	ksDdjqjfc6FMarl1pZyxKd9EqpP7mI8VF1jlbGHsKi/S4LVwYqKPOvBQFkmK+y5w
	U8HuA2icWE6wUOtQowCmseVTBQ/wIvH+VQcgVHNA1sjOS11Wmujpx0zw6IM8B5KF
	chlHROuXv6rEpEtnxb3Ia20Um1E=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: setup-x86.exe v2.893 has stopped working
To: The Cygwin Mailing List <cygwin@cygwin.com>
References: <CAFWoy7HuhsSgavPNes7JVdV0ydrBQo5pKO6Z2WPDkQXdJjxP7g@mail.gmail.com> <638c7199-a6f9-3bc7-fb16-f82a16dfb639@gmail.com> <CAFWoy7HURnK9vX35V2PEL5jG3JKSMv+UpgOpKXnGcteEGPPbUA@mail.gmail.com> <d33edbea-d849-bda7-5ea6-b9aeda12be5c@cornell.edu> <e140b4b6-df11-549f-334d-3cb27c89d23f@dronecode.org.uk> <CAFWoy7HqmDSEDt0FxeTyJ4y4qU53_60bLiBR=Jcg5-VNFteAYA@mail.gmail.com> <78ec8158-7308-a37a-b990-3a917305e575@gmail.com> <CAFWoy7FCi+SOTJKV_R6P0mf+sqwACWeZOWqGyLw-RwW4Tk4ACg@mail.gmail.com>
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <45a0d76c-67c0-8a0d-e30a-2d022e8b80f5@dronecode.org.uk>
Date: Wed, 3 Oct 2018 17:53:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAFWoy7FCi+SOTJKV_R6P0mf+sqwACWeZOWqGyLw-RwW4Tk4ACg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 03/10/2018 16:40, Keith Christian wrote:
> Finished building setup.exe using the
> http://sourceware.org/git/cygwin-apps/setup.git source.
> 
> 10/03/2018  07:45 AM        23,423,478 setup-2.893.x86.dbg
> 10/03/2018  08:57 AM        29,231,233 setup.exe  (version
> 2.893-3-ge084ed (32 bit)) in the splash screen.
> 
> setup.exe aborts at approximately the same point, while parsing
> setup.ini.  When it aborts I see a windows dialog box offering to send
> Microsoft more info about the problem, which I denied.
> 
> To proceed, I need a bit of help in the basics of gdb to continue
> troubleshooting.

If you've build setup.exe from source using the default make target 
(i.e. 'make' rather than 'make strip' or 'make upx'), then the built 
executable is unstripped and contains symbols (so you don't need the 
.dbg file; which corresponds to a different build in any case...)

Something like the following should work:

gdb setup.exe
run
[reproduce crash]
bt full

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