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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=DRg7x1WZ4PoRCsR/jdPF1sN+fmBKp
	SONa9AiNObWSElPQPH3oMgzrVNsDT5N3vL+NUBxAjrMbDQ2wNlQtWYP5pIEUpXeh
	gF2ayWNhNq9uwQoRVHQsulYK2VNcB3eviSiZ9CUDCTpvi5O5HMkrzrXHGtbk90E7
	/QOBWHji40xbhA=
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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=TfXobh8rdqkR8CrkLpx1elBGIr4=; b=xs/
	nUPIlREYliMieHh/tWvqPeZ0RnToaas6v7CJ+sMurB15HdQzW0B3o6nkldLlZzbk
	o4zPfm4Ig/qILsDSDYCPgB5BNxRFMeD4LuWhmvpc4UzgbLM2j54dcKOJ9WUIw7t7
	XEloVGd2Tn/QckADVPqDla93eV4ypGVEY4wJ9idY=
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=0.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	nbfkord-smmo06.seg.att.com
X-MXL-Hash:	5354a9397c0c481a-c9e34cf99092d8cd933e1e1491127a1be2e75237
From:	"KARR, DAVID" <dk068x AT att DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	RE: Fatal error from Cygwin emacs-w32 every day or so
Date:	Mon, 21 Apr 2014 05:14:11 +0000
Message-ID:	<B8D164BED956C5439875951895CB4B222660E6D2@CAFRFD1MSGUSRIA.ITServices.sbc.com>
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> <534CB0AF DOT 2040504 AT cornell DOT edu> <83y4z7jcb3 DOT fsf AT gnu DOT org> <534D5AB8 DOT 6030201 AT cornell DOT edu> <535308D8 DOT 1070200 AT cornell DOT edu> <B8D164BED956C5439875951895CB4B222660C8D2 AT CAFRFD1MSGUSRIA DOT ITServices DOT sbc DOT com>
In-Reply-To:	<B8D164BED956C5439875951895CB4B222660C8D2@CAFRFD1MSGUSRIA.ITServices.sbc.com>
MIME-Version:	1.0
X-RSA-Inspected:	yes
X-RSA-Classifications:	public
X-AnalysisOut:	[v=2.0 cv=QZ3RSLnv c=1 sm=1 a=xwOvzTHDVLE4u4nGvK72ag==:17 a]
X-AnalysisOut:	[=94PlVXF_xlIA:10 a=ofMgfj31e3cA:10 a=YnP4VLJI-BoA:10 a=BLc]
X-AnalysisOut:	[eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R]
X-AnalysisOut:	[AAAA:8 a=v_eIKD0wAAAA:8 a=kU5xYpk24MVtQNq8nfsA:9 a=CjuIK1q]
X-AnalysisOut:	[_8ugA:10]
X-Spam:	[F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM:	<dk068x AT att DOT com>
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id s3L5Elo2012827

> -----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 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)
> > >>>>      @/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:
--------------------
Program received signal SIGTRAP, Trace/breakpoint trap.
0x000007fefd773ca3 in KERNELBASE!DebugBreak ()
   from /c/Windows/system32/KERNELBASE.dll
(gdb)
(gdb) bt
#0  0x000007fefd773ca3 in KERNELBASE!DebugBreak ()
   from /c/Windows/system32/KERNELBASE.dll
#1  0x000000010056e6cb in ?? ()
#2  0x0000000000429318 in ?? ()
#3  0x000000010091ccd8 in ?? ()
#4  0x0000000000000000 in ?? ()
(gdb)
--------------------

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

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