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:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=sIWpm/28v5TUWKSjYCO4xgbA0ejuf4HzBpn8J1zoRWP
	KjOl0Sr+l9XFvjWxLEFFMtKa7QTR/2sCUSuGcUPGOUv/gYtrvbB1ziahUhi+OHJE
	BTY0EJ3Ef+kboeHy+Pv2xIDaR5FM6HD2Xgfa1hekyceWthtgkzwuqpWUlynw/2YA
	=
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:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=pBF5xIg0rRuSwYFE3IT+OmQKr6c=; b=GML9lWPY9Z1o4boId
	ikPOFI3hZYN6u1jn7fwsSSMk/Uz5n7lTXlFeX8oKjf9Bs159AD9vldHjQSiAUUX1
	o3xvC9PnLlf53m3hl9gXlU21kPtcSuHADeCfgdm8HZYLAD4fJrN05g1wlzZR8Zgx
	GuNb5O9mSkeRhmfRusyzLHdBZo=
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
X-Spam-SWARE-Status:	No, score=-4.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-CornellRouted:	This message has been Routed already.
Message-ID:	<520D87C0.7030501@cornell.edu>
Date:	Thu, 15 Aug 2013 22:00:32 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 64-bit emacs crashes a lot
References:	<51F3151D DOT 7040000 AT cs DOT utoronto DOT ca> <51F33565 DOT 1090406 AT cornell DOT edu> <51F33F52 DOT 4060405 AT cs DOT utoronto DOT ca> <51FB1D9E DOT 5090102 AT cs DOT utoronto DOT ca> <20130802080211 DOT GA18054 AT calimero DOT vinschen DOT de> <51FB9228 DOT 2020309 AT cornell DOT edu> <51FBA100 DOT 90005 AT cs DOT utoronto DOT ca> <51FD5462 DOT 5020400 AT cs DOT utoronto DOT ca> <51FFBDFF DOT 7040501 AT cornell DOT edu> <51FFC4F2 DOT 8080909 AT cs DOT utoronto DOT ca> <5203D89E DOT 6030801 AT cornell DOT edu> <5203DCCA DOT 1010105 AT cs DOT utoronto DOT ca> <5205B364 DOT 8090007 AT cs DOT utoronto DOT ca> <52064730 DOT 50404 AT cornell DOT edu> <"52065B3C DOT 6060104 AT cs DOT utoronto <520CCA41.3000107"@cs.utoronto.ca> <520D089A DOT 1020806 AT cornell DOT edu> <83ioz6op5v DOT fsf AT gnu DOT org> <520D4036 DOT 8010303 AT cs DOT utoronto DOT ca> <520D44B9 DOT 7090206 AT cornell DOT edu> <520D4725 DOT 3030503 AT cs DOT utoronto DOT ca> <520D4F07 DOT 8050007 AT cornell DOT edu> <520D4FF7 DOT 5040405 AT cornell DOT edu> <520D5AA6 DOT 2010003 AT cs DOT utoronto DOT ca> <520D5F29 DOT 1040307 AT cornell DOT edu> <520D792D DOT 7090008 AT cs DOT utoronto DOT ca>
In-Reply-To:	<520D792D.7090008@cs.utoronto.ca>

On 8/15/2013 8:58 PM, Ryan Johnson wrote:
> On 15/08/2013 7:07 PM, Ken Brown wrote:
>> On 8/15/2013 6:48 PM, Ryan Johnson wrote:
>>> On 15/08/2013 6:02 PM, Ken Brown wrote:
>>>> On 8/15/2013 5:58 PM, Ken Brown wrote:
>>>>> On 8/15/2013 5:24 PM, Ryan Johnson wrote:
>>>>>> On 15/08/2013 5:14 PM, Ken Brown wrote:
>>>>>>> On 8/15/2013 4:55 PM, Ryan Johnson wrote:
>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>> ___chkstk_ms () at
>>>>>>>> /usr/src/debug/gcc-4.8.1-1/libgcc/config/i386/cygwin.S:146
>>>>>>>
>>>>>>> You're not using the latest gcc, which is 4.8.1-3.  Any chance that
>>>>>>> that's your problem?
>>>>>> Heh. I actually do have the latest gcc, but somehow the upgrade
>>>>>> didn't
>>>>>> pick up the debug package (which showed as not installed in
>>>>>> setup.exe).
>>>>>> I have manually upgraded it now.
>>>>>
>>>>> OK.  But doesn't the above show that the crash is occurring in gcc,
>>>>> not
>>>>> emacs?
>>>>>
>>>>>> BTW, how do you compile emacs from the sources given? I tried
>>>>>> untarring
>>>>>> and patching, but I get the message:
>>>>>>> configure: error: Emacs hasn't been ported to
>>>>>>> `x86_64-unknown-cygwin'
>>>>>>> systems.
>>>>>>> Check `etc/MACHINES' for recognized configuration names.
>>>>>
>>>>> One of the patches changes configure.ac, so you have to run autoreconf
>>>>> after applying it.
>>>>
>>>> Or it might be 'autoreconf -I m4'.
>>>
>>> Something is still wrong:
>>>
>>> $ cd /scratch
>>> $ tar xaf /usr/src/emacs-24.3.tar.xz
>>> $ patch -p1 </usr/src/emacs-24.3-5.cygwin.patch
>>> patching file emacs-24.3/CYGWIN-PATCHES/emacs-X11.postinstall
>>> patching file emacs-24.3/CYGWIN-PATCHES/emacs-X11.preremove
>>> patching file emacs-24.3/CYGWIN-PATCHES/emacs-w32.postinstall
>>> patching file emacs-24.3/CYGWIN-PATCHES/emacs-w32.preremove
>>> patching file emacs-24.3/CYGWIN-PATCHES/emacs.postinstall
>>> patching file emacs-24.3/CYGWIN-PATCHES/emacs.preremove
>>> $ cd emacs-24.3
>>> $ autoreconf -I m4
>>> $ ./configure CFLAGS='-g -0g -fsanitize=address'
>>> LDFLAGS='-fsanitize=address' --without-all
>>> checking for a BSD-compatible install... /usr/bin/install -c
>>> checking whether build environment is sane... yes
>>> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
>>> checking for gawk... gawk
>>> checking whether make sets $(MAKE)... yes
>>> checking build system type... x86_64-unknown-cygwin
>>> checking host system type... x86_64-unknown-cygwin
>>> configure: error: Emacs hasn't been ported to `x86_64-unknown-cygwin'
>>> systems.
>>> Check `etc/MACHINES' for recognized configuration names.
>>>
>>> In particular, it doesn't look like the patch actually patches any emacs
>>> files at all... do I need to pull all past versions of the source
>>> package as well or something?
>>
>> The source package for emacs-24.3-5 contains lots of patches that you
>> didn't apply:
>>
>>     nox_mouse.patch
>>     w32_encoding.patch
>>     configure.ac.patch
>>     syms_of_cygw32.patch
>>     image_background.patch
>>     w32term.w32_init.patch
>>     unexcw.patch
>>     memory_warnings.patch
>>     24.3-4_nt_icon.patch
>>     nonbootstrap_static_heap.patch
>>     24.3_memalign.patch
> I see... that would explain it.
>
> For future reference, though, how does one go about discovering which
> patches to apply? Most of those file names don't associate them with
> emacs in any obvious way, and `cygcheck -f' claims that none of them
> belong to any package... do you have to go dig up the source package's
> package file and look inside?

Take a look at emacs.cygport.  It shows you exactly how the package was 
built, including patches.

Ken


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