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=IBmxnZi0BxnRdmZIQd00203gFAhlsx24axQ19CU4fIB
	3bVl/AG+V7Scp4qaDB0KWlm+b/VyL9tTXTJBr3I0kdZplyj1Q+FaYV9kIKN9EXVZ
	HIyuSv7W0N/vOGKF3Mw2LD2OYpf70ckut96HAc2ZIlext6DAWBA89oNAEw6wn7HM
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <537368BA.9070009@cornell.edu>
Date: Wed, 14 May 2014 08:59:38 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Emacs-w32... crashing problem
References: <1400016356.24737.YahooMailNeo@web185401.mail.gq1.yahoo.com>
In-Reply-To: <1400016356.24737.YahooMailNeo@web185401.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 5/13/2014 5:25 PM, Zdzislaw Meglicki wrote:
> Ken Brown writeth:
>
>> Please describe the crash in more detail.
>> What were you doing when it happened?  Did
>> the window just disappear, or did you get
>> a dialogue box asking if you want to attach
>> a debugger?  Did you get any messages in the
>> terminal that emacs was started from?  Is
>> there a stackdump file?
>
> The window just disappeared. There was no dialogue
> box that would let me attach gdb to the process.
> I did not run it under "-Q" at the time, and I do
> not have a stackdump file (I deleted it).
>
> I will keep an eye on this and if it crashes
> again, hopefully letting me attach gdb, I'll
> post a backtrace and the stackdump file, if you'd
> like to have a look at it.

You don't have to wait for it to crash.  If you have an emacs running 
right now, you can go ahead and attach gdb and then continue working in 
emacs.  Or you can just start emacs under gdb to begin with.

One other thing you could try is to install a Cygwin snapshot 
(http://cygwin.com/snapshots/).  There were some problems with exception 
handling on 64-bit Cygwin.  Corinna fixed most of these for 
cygwin-1.7.29, but I think there was one further fix after that.

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