This is the mail archive of the
mailing list for the Cygwin project.
Re: Fatal error from Cygwin emacs-w32 every day or so
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Date: Mon, 14 Apr 2014 21:08:15 -0700
- Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
- Authentication-results: sourceware.org; auth=none
- 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>
On 4/14/2014 11:31 AM, KARR, DAVID wrote:
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 (
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple