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=LoaGQKR3eQmwXyBWChRkE6EEG5K1JOaJQg5bq8JMurD
	VOIL93xsxog85gzC6ctYC2UtNdxgdsqv3DiCriAW7OEctvTcYbEVULFCNx85l0j2
	GIFYaEk1/Om65UhhEGusCNdDYsqaFK6GeH/OQYWaWXh9dU/D/1NRESaoT5/2D2D4
	=
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: <54217D60.6080400@cornell.edu>
Date: Tue, 23 Sep 2014 10:02:08 -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 AT cygwin DOT com
Subject: Re: Fwd: Re: Strange gdb backtraces on 64-bit Cygwin
References: <d5f51edd911833fc460a08bbf5a80321 AT mhoenicka DOT de>
In-Reply-To: <d5f51edd911833fc460a08bbf5a80321@mhoenicka.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 9/23/2014 9:23 AM, Markus Hoenicka wrote:
> At 2014-09-23 14:31, Ken Brown was heard to say:
>>
>> So I think it's pretty clear that the strange backtrace I observed
>> with gdb-7.6.50-4 on 64-bit Cygwin was indeed due to a deficiency in
>> gdb.
>>
>> I hope that people who have been experiencing emacs crashes with
>> "impossible" backtraces will update to gdb-7.8-2.
>>
>
> Hi,
>
> I might be dense somehow, but the two emacs crashes with said
> "impossible" backtraces that I reported yesterday [1][2] were observed
> with the gdb version that you recommend:
>
> $ gdb -version
> GNU gdb (GDB) 7.8
> [...]
>
> $ cygcheck -f /usr/bin/gdb
> gdb-7.8-2
>
> Are you sure this is all it takes to get sane backtraces?

The "impossible" backtraces that you were getting earlier were the ones 
that showed run_timers in Thread 2.  This problem didn't occur with the 
backtraces that you reported yesterday.  The only problem with those 
backtraces was the lack of detail in Thread 1.  Eli suggested one 
possible explanation.  Another is that the stack had gotten messed up by 
whatever caused the crash, so that gdb was unable to unwind it.  If we 
ever get any clue as to what's causing these crashes, we might come up 
with a reasonable place to set a breakpoint in order to get a useful 
backtrace.

By the way, I'm sure that one or more of your threads are created by 
Glib.  So installing the debuginfo for Glib as I suggested yesterday 
might help, at least in those cases where the crash/abort involves Glib.

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