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=cuF99vzoZx4IbnVVq0K2mudhh56vgoClkmnPMvsCY7M
	4hPrvmhdxfNWLp5L2s66gM5eqXuI22X/bIbprmA61/JBXzzK+RedYW3IgDArL0qd
	Bl++tDbos/Pss4YT3WTn2R10kiVfGLCP61kldAWypqBeZui5EeDlWVqXlmqN/JFw
	=
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=DbIj5mwYAF0KGCFar/d9t64yWNA=; b=Zl4AzHfVhQscIgreX
	m6J74jUWMCRfazeBq2qSgm0gdeOTWn3emVdzkdqnIkR59hlMDFWjtLbAopDOg3e1
	L4Ly759bS9vGNLcodMaTiDiGP69JG6IIfMYWgBEcJ3sqfgDd+pY6FvqeLy03KGQw
	k5HqmOxW5KQsVuDJqsA49QReak=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: limerock02.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Message-ID: <534CB0AF.2040504@cornell.edu>
Date: Mon, 14 Apr 2014 21:08:15 -0700
From: Ken Brown <kbrown AT cornell DOT 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 AT cygwin DOT com
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
References: <B8D164BED956C5439875951895CB4B2225C00EA9 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <534B2EFE DOT 4010509 AT cornell DOT edu> <B8D164BED956C5439875951895CB4B2225C01C84 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com>
In-Reply-To: <B8D164BED956C5439875951895CB4B2225C01C84@WABOTH9MSGUSR8C.ITServices.sbc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 4/14/2014 11:31 AM, KARR, DAVID wrote:
>> -----Original Message-----
>> Of Ken Brown
>> Sent: Sunday, April 13, 2014 5:43 PM
>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
>>
>> On 4/13/2014 10:53 AM, KARR, DAVID wrote:
>>> I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so, I
>> get a "fatal error" dialog from emacs-w32.  It asks me if I want to debug
>> it, but I'm not sure what info I could pull from gdb that would be useful.
>>
>> A gdb backtrace might or might not be helpful.  I would start with other
>> things first (see below).
>
> 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 AT entry=0, nsecs=nsecs AT entry=0,
>      read_kbd=read_kbd AT entry=-1, do_display=do_display AT entry=true,
>      wait_for_cell=wait_for_cell AT entry=4304630834,
>      wait_proc=wait_proc AT entry=0x0, just_wait_proc=just_wait_proc AT entry=0)
>      at /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.

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