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: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 = 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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=DA6BiUJbRJYLVbWKiFZG4sjxieo=; b=bYIB4+CKrVsBE4eIf aZ29TTNKearIUmdYueuDt82l9XwuByF9Wi0EAGzkA3SjP2zEvrHcaVoTjNej+/DP 3NW0YhJpVoGbltBdHc1deHYy6ptSslwcyK7Rf9wSDiAC6RWAqgRzQSk20HwTu+1V u+mev/irDpXEvGSt1igdWzAwvw= 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=-2.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: limerock01.mail.cornell.edu X-CornellRouted: This message has been Routed already. Message-ID: <54217D60.6080400@cornell.edu> Date: Tue, 23 Sep 2014 10:02:08 -0400 From: Ken Brown 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: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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