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=RLxOHTYYYAjHYEmJcrh3fAZ/YX7JWLrWIaiWaHyy39w
	QQgAEcUsnYAmO3lUJKkWd/HW21pX6BG025kSF1bW85DJDugOEJ4Z9dym+RV9zoxL
	HJYK14HzaTv2TnSRFwNK/YTlxt/WSbYiXogd9L7ZXxrK4f9JNBSlIuUJHSnb1LJI
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <53BBF86B.7090801@cornell.edu>
Date: Tue, 08 Jul 2014 09:55:55 -0400
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.6.0
MIME-Version: 1.0
To: cygwin <cygwin AT cygwin DOT com>
Subject: Re: Emacs-w32... Still Crashing
References: <1404760352 DOT 3454 DOT YahooMailNeo AT web185401 DOT mail DOT gq1 DOT yahoo DOT com>
In-Reply-To: <1404760352.3454.YahooMailNeo@web185401.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 7/7/2014 3:12 PM, Zdzislaw Meglicki wrote:
> The current version of Emacs that I have is
> emacs                   24.3.91-1            OK
> emacs debuginfo         24.3.91-1            OK
> emacs-el                24.3.91-1            OK
> emacs-w32               24.3.91-1            OK
> emacs-X11               24.3.91-1            OK
>
> Cygwin is
> Cygwin DLL version info:
> DLL version: 1.7.30
> DLL epoch: 19
> DLL old termios: 5
> DLL malloc env: 28
> Cygwin conv: 181
> API major: 0
> API minor: 272
> Shared data: 5
> DLL identifier: cygwin1
> Mount registry: 3
> Cygwin registry name: Cygwin
> Program options name: Program Options
> Installations name: Installations
> Cygdrive default prefix:
> Build date:
> Shared id: cygwin1S5
>
> Windows is
>
> Windows 8.1 Pro on AMD A8-5500 APU, 3.20 GHz, 64-bit OS, x64 CPU
>
> These days, Emacs no longer crashes as often as it used to.

That's good to hear.

> So, there's been nothing to report until now. Emacs-w32 hanged
> and produced the "do you want to enter debugger" window,
> with the following backtrace produced by gdb:
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 4532.0xa100]
> 0x00007ff974f39e3b in KERNELBASE!DebugBreak () from /cygdrive/c/WINDOWS/system32/KERNELBASE.dll
> (gdb) bt
> #0  0x00007ff974f39e3b in KERNELBASE!DebugBreak () from /cygdrive/c/WINDOWS/system32/KERNELBASE.dll
> #1  0x000000010061a7a4 in emacs_abort () at /usr/src/debug/emacs-24.3.91-1/src/w32fns.c:8474
> #2  0x000000010043b702 in check_message_stack () at /usr/src/debug/emacs-24.3.91-1/src/xdisp.c:10993
> #3  0x00000001004fd763 in shut_down_emacs (sig=0, stuff=4305643570) at /usr/src/debug/emacs-24.3.91-1/src/emacs.c:2042
> #4  0x00000001004fd591 in Fkill_emacs (arg=60) at /usr/src/debug/emacs-24.3.91-1/src/emacs.c:1952
> #5  0x00000001004fb159 in terminate_due_to_signal (sig=15, backtrace_limit=40) at /usr/src/debug/emacs-24.3.91-1/src/emacs.c:360
> #6  0x0000000100520429 in handle_fatal_signal (sig=15) at /usr/src/debug/emacs-24.3.91-1/src/sysdep.c:1630
> #7  0x000000010052035d in deliver_process_signal (sig=15, handler=0x100520411 ) at /usr/src/debug/emacs-24.3.91-1/src/sysdep.c:1570
> #8  0x0000000100520444 in deliver_fatal_signal (sig=15) at /usr/src/debug/emacs-24.3.91-1/src/sysdep.c:1636
> #9  0x0000000180070c8a in _cygtls::call_signal_handler (this=0x43ce00) at /usr/src/debug/cygwin-1.7.30-1/winsup/cygwin/exceptions.cc:1463
> #10 0x0000000180111db8 in sigdelayed () from /usr/bin/cygwin1.dll
> #11 0x0000000100a2e832 in bss_sbrk_buffer ()
> #12 0x0000000000000000 in ?? ()

Thanks.  All I can see from this is that a SIGTERM was generated, 
causing emacs to abort, but maybe someone else can see more.

Grasping at straws, as usual, I wonder if these mysterious crashes could 
be related to a bug that Corinna just fixed:

   https://cygwin.com/ml/cygwin-cvs/2014-q3/msg00004.html

Corinna, is this plausible?  If so, maybe Gustav should try the next 
snapshot of the Cygwin DLL.  (The current one doesn't seem to have this 
fix in it.)

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