X-Recipient: archive-cygwin AT delorie DOT com 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= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=EZmsRfLGCwT+vg9NGQ8njwdppI o=; b=tJyBhFTK8/E4BhFo60CYlLXzOKO2MHx/F/JwfGkC7vVpSX/dYwe2qd88GG 9DFk3xEEUj61bU5eE1oRELaYGJT1C6p4K0qeWyW2O4kKNEMKlfbBczoRPsedYCSi 1PLrL39AsQw2xR5sqNZz9aE+x0Vh0AD6t9InALIeu7TPopwfE= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: smtprelay02.ispgateway.de 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 To: cygwin AT cygwin DOT com Subject: Re: Fwd: Re: Strange gdb backtraces on 64-bit Cygwin In-Reply-To: <54217D60.6080400@cornell.edu> References: <54217D60 DOT 6080400 AT cornell DOT edu> Message-ID: X-Sender: markus DOT hoenicka AT mhoenicka DOT de User-Agent: Roundcube Webmail X-Df-Sender: bWFya3VzLmhvZW5pY2thQG1ob2VuaWNrYS5kZQ== X-IsSubscribed: yes 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