DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=F4y9mradF0Nw1wjknIGAHJ2FlOLWc
	EEXnnaXxPJh7GqIJ4za2diQhDdmJs1bQTgSFIr72TcqgCYl7rJGvyx2dsQn/pwB5
	aAEwxPeZHstpphkhdGuBMoRTRP6lLdNji/gScuBCItvRYA/XxuY41mYTHlxj1jBy
	JdxMHYL6JUPVWw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: Michael Wild <themiwi@gmail.com>
Date: Mon, 21 Jan 2019 09:03:32 +0100
Message-ID: <CAALQ5rnmuEtm6208hQd2qo9FKWmdT=N7RFEg5QqqaZeCgoG3vQ@mail.gmail.com>
Subject: UPX compressed setup-x86_64.exe crashes on Win10
To: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Type: text/plain; charset="UTF-8"

Dear all

I recently got a new laptop at work with Win10 (1709). I went ahead,
downloaded setup-x86_64.exe and wanted to install Cygwin. However, it
crashes with a segmentation fault. Trying to get to the bottom of
things I got the sources on my old laptop and compiled the thing,
copied it to the new laptop, and surprisingly it worked. I then tried
the stripped version. Again, it worked. However, when I tried to run
the UPX compressed executable, I got the segfault again.

Anybody else experiencing this? I tried trawling through the mailing
list, but nothing specific turned up. Maybe this is an interaction
with the BLODA imposed on me by our company IT policy. But then I'd
expect others to have seen this issue too.

Cheers

Michael

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