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=y7u1BIG2aiOnmKAZx6H7Egj9T1VnLFk9gcxj76z8t9e
	Hmh7kzlpLuj1O/MhHFF1wqwXbH0VttZx7z9wxmFN1lsKIU5nY9Pl8N6d/AuDozvc
	dfwEbOv43foKhmrAjBWwB6TtEHaRFQxo9Rm/DmzI08Ai5MWK3LgHsz5Gv43e0iao
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <520D85A5.1030402@cs.utoronto.ca>
Date: Thu, 15 Aug 2013 21:51:33 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: 64-bit emacs crashes a lot
References: <51F3151D.7040000@cs.utoronto.ca> <51F33565.1090406@cornell.edu> <51F33F52.4060405@cs.utoronto.ca> <51FB1D9E.5090102@cs.utoronto.ca> <20130802080211.GA18054@calimero.vinschen.de> <51FB9228.2020309@cornell.edu> <51FBA100.90005@cs.utoronto.ca> <51FD5462.5020400@cs.utoronto.ca> <51FFBDFF.7040501@cornell.edu> <51FFC4F2.8080909@cs.utoronto.ca> <5203D89E.6030801@cornell.edu> <5203DCCA.1010105@cs.utoronto.ca> <5205B364.8090007@cs.utoronto.ca> <52064730.50404@cornell.edu> <"52065B3C.6060104@cs.utoronto <520CCA41.3000107"@cs.utoronto.ca> <520D089A.1020806@cornell.edu> <83ioz6op5v.fsf@gnu.org> <520D4036.8010303@cs.utoronto.ca> <520D44B9.7090206@cornell.edu> <520D4725.3030503@cs.utoronto.ca> <520D4F07.8050007@cornell.edu> <520D4FF7.5040405@cornell.edu> <520D5AA6.2010003@cs.utoronto.ca> <520D60D3.3050505@cs.utoronto.ca> <520D6707.4040902@cornell.edu>
In-Reply-To: <520D6707.4040902@cornell.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 15/08/2013 7:40 PM, Ken Brown wrote:
> On 8/15/2013 7:14 PM, Ryan Johnson wrote:
>> On 15/08/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
>> Ah, it seems there's a /usr/src/configure.ac.patch that happens to
>> belong to emacs...
>>
>> ... but unfortunately it seems that -fsanitize is only supported on
>> Linux and Darwin right now, so there's little reason to build emacs
>> unless you could use some particular information that a debug build
>> provides. Rats.
>
> But a build without optimization would make your backtraces more useful.
I'm not sure even a perfect stack trace will be very useful if memory 
corruption is the culprit, though. All it will do is give us even 
clearer detail about exactly what got clobbered, but with little 
additional info about what did the clobbering.

That said, I'm game if you have anything in particular you'd like more 
detail on; just let me know what you'd like to see and I'll do my best 
to dig it up. Meanwhile, I'll fire off the debug build.

Ryan


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