From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29907 invoked by alias); 18 Sep 2014 06:35:22 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 29885 invoked by uid 89); 18 Sep 2014 06:35:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: smtprelay04.ispgateway.de Received: from smtprelay04.ispgateway.de (HELO smtprelay04.ispgateway.de) (80.67.29.8) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Thu, 18 Sep 2014 06:35:18 +0000 Received: from [80.67.16.118] (helo=webmail.df.eu) by smtprelay04.ispgateway.de with esmtpa (Exim 4.68) (envelope-from ) id 1XUVJB-0003Gi-6r; Thu, 18 Sep 2014 08:35:13 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 18 Sep 2014 09:23:00 -0000 From: Markus Hoenicka To: Ken Brown Cc: cygwin , Eli Zaretskii Subject: Re: Strange gdb backtraces on 64-bit Cygwin In-Reply-To: <5419FB60.5090908@cornell.edu> References: <5419FB60.5090908@cornell.edu> Message-ID: <8e8c385f5fb29ba3d3853eeee61b34f6@mhoenicka.de> X-Sender: markus.hoenicka@mhoenicka.de User-Agent: Roundcube Webmail X-Df-Sender: bWFya3VzLmhvZW5pY2thQG1ob2VuaWNrYS5kZQ== X-IsSubscribed: yes X-SW-Source: 2014-09/txt/msg00285.txt.bz2 At 2014-09-17 23:21, Ken Brown was heard to say: > There have been many bug reports involving crashes or assertion > failures in emacs-X11 or emacs-w32 on 64-bit Cygwin. Many of these > reports include gdb backtraces that don't make sense. The one I'm > looking at right now is emacs bug#17753. I'll try to make this email > self-contained, but anyone interested in the context should start at > > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17753#47 > > The situation in that bug report is that a gdb backtrace showed a call > to the emacs function "run_timers" in Thread 2, which shouldn't > happen. (It should only be called in the main thread.) There was > speculation as to whether this could be the cause of the crash. An > alternative theory is that the gdb backtrace is bogus. I'm pretty > sure that the OP (Markus) was running gdb-7.6.50-4. His report was > about emacs-X11, but I've observed similar backtraces for emacs-w32. > This is just to confirm the suspected version of gdb on the OP's box: $ cygcheck -f /usr/bin/gdb gdb-7.6.50-4 $ gdb -v GNU gdb (GDB) 7.6.50.20130728-cvs (cygwin-special) [...] 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