DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=ysYNMtFu0QpY6fTSH2rB
	9J2l4tUuDh0OJCaZRWKy51Abm+0I/dnrqdMzD1M9PdbCgsv7AqKx0DtoHIxDz02L
	fVyZZYpIT/7tGP8h5e1/yqVuQsrDa0HLjHjEQ3Hb1e5vCgkXcprFikfKnqShCR3g
	W0BffOF3CgBsrTAMjgG9f/o=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 23 Sep 2014 16:28:09 +0200
From: Markus Hoenicka <markus.hoenicka@mhoenicka.de>
To: cygwin@cygwin.com
Subject: Re: Fwd: Re: Strange gdb backtraces on 64-bit Cygwin
In-Reply-To: <54217D60.6080400@cornell.edu>
References: <d5f51edd911833fc460a08bbf5a80321@mhoenicka.de> <54217D60.6080400@cornell.edu>
Message-ID: <ec524cf884ca057bef9733645d00faa5@mhoenicka.de>
User-Agent: Roundcube Webmail

At 2014-09-23 16:02, Ken Brown was heard to say:
> 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.
> 

Thanks for the clarification. I did install the Glib debuginfo as you 
suggested earlier today.

regards,
Markus

-- 
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38


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