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=q3EEZXmGrpS23QE2I5QnBhLSQf4yhLPN6+jvFv98yfO
	gGK5hwGzrTzL1rQYl6oM1V2p7Mkd8QfQEA9hxwX1CJ9GclwHHcNkRRkJX1V2e0Vp
	Rny3UGq+5Doztadff0a7gX03nwF++hTzq0EF3n0KzZWa1sFPynVzi+0hDUXXQIfM
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5354FDD8.9090605@cornell.edu>
Date: Mon, 21 Apr 2014 07:15:36 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
References: <B8D164BED956C5439875951895CB4B2225C00EA9@WABOTH9MSGUSR8C.ITServices.sbc.com> <534B2EFE.4010509@cornell.edu> <B8D164BED956C5439875951895CB4B2225C01C84@WABOTH9MSGUSR8C.ITServices.sbc.com> <534CB0AF.2040504@cornell.edu> <83y4z7jcb3.fsf@gnu.org> <534D5AB8.6030201@cornell.edu> <535308D8.1070200@cornell.edu> <B8D164BED956C5439875951895CB4B222660C8D2@CAFRFD1MSGUSRIA.ITServices.sbc.com> <B8D164BED956C5439875951895CB4B222660E6D2@CAFRFD1MSGUSRIA.ITServices.sbc.com>
In-Reply-To: <B8D164BED956C5439875951895CB4B222660E6D2@CAFRFD1MSGUSRIA.ITServices.sbc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 4/21/2014 1:14 AM, KARR, DAVID wrote:
>> -----Original Message-----
>> Of KARR, DAVID
>> Sent: Saturday, April 19, 2014 6:19 PM
>> Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
>>
>>> -----Original Message-----
>>> Of Ken Brown
>>> Sent: Saturday, April 19, 2014 4:38 PM
>>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
>>>
>>> On 4/15/2014 12:13 PM, Ken Brown wrote:
>>>> On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
>>>>>> Date: Mon, 14 Apr 2014 21:08:15 -0700
>>>>>> From: Ken Brown
>>>>>>
>>>>>>> I just saw it die, and this is the bt I get:
>>>>>>>
>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>> 0x0000000100551354 in wait_reading_process_output (
>>>>>>>        time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
>>>>>>>        read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true,
>>>>>>>        wait_for_cell=wait_for_cell@entry=4304630834,
>>>>>>>        wait_proc=wait_proc@entry=0x0,
>>>>>>> just_wait_proc=just_wait_proc@entry=0)
>>>>>>>       @/usr/src/debug/emacs-24.3-7/src/process.c:4677
>>>>>>> 4677                      if (wait_proc->gnutls_p /* Check for
>> valid
>>>>>>> process.  */
>>>>>>
>>>>>> This backtrace doesn't make sense.  If you look at the source code,
>>>>>> you'll see that if wait_proc is NULL on entry to
>>>>>> wait_reading_process_output, then line 4677 is never reached.  I'm
>> not
>>>>>> sure what would cause a bogus backtrace like this.  BLODA?
>>>>>> Optimization?
>>>>>>
>>>>>> In any case, I suggest that you wait a week until I have a chance to
>>>>>> build a pretest of 24.4 for you to try.  I'll build it without
>>>>>> optimization to make debugging easier.
>>>>>
>>>>> This is a known problem with GnuTLS support, it was solved in the
>>>>> Emacs repository last November (bzr revision 114956, if someone wants
>>>>> the diffs), and surely should be solved in the upcoming Emacs 24.4.
>>>>
>>>> Thanks, Eli!  In that case I'll make a new release of emacs-24.3 with
>>>> that patch applied, to see if it resolves the issue for the OP.
>>>
>>> I've rebuilt emacs-24.3 with the gnutls fix.  David and Achim (and
>>> anyone else who's been experiencing these crashes), please try the
>>> following binary and let me know if it solves the problem:
>>>
>>>      http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
>>>
>>> You might have to do "chmod +x emacs-w32.exe" after uncompressing it.
>>>
>>> If it fixes the problem, I'll issue a new release of emacs-24.3.  If
>>> not, I'll build a pretest of emacs-24.4 for you to try.
>>
>> Ok.  It's running.  As it only fails after random intervals, I'll have to
>> keep it running for a while.  I'll give it a day or so.
>
> I came back to my computer and saw two dialogs, one saying that my VPN connection had died (that happens from time to time), and the other the Emacs failure dialog.  I started this executable from gdb, but it's saying that it doesn't have symbols, so the stacktrace probably isn't helpful, but this is what I saw:

Right.  I just supplied a stripped binary for a quick test.  It's not 
suitable for debugging.

> I've started it again, but not in gdb this time.

If it crashes again, I'll build a pretest of 24.4 without optimization 
and issue it as a test release.

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