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:cc:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=jMslY6eG4hCQ1BVGAtoB
	eWm4JeFP35OEaiPINvg5W8s+U4e46TCRzvzccv5KwGKJXm976X4U/bgvAHVTroDP
	ZnMzu2kYznjyo0MDxtFR9GgY6KpuL4xvyqcL6tUO93I3d74mAnRrvDn0t5yARd2y
	LIZ3V4P0yO9qY/FruXJowxY=
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:cc:subject:in-reply-to
	:references:message-id; s=default; bh=JpgDvSXQbEuLtLPonCvuOHRM7+
	4=; b=isuEUhw2JD+BenSsGCBao3GfPxjIzRggztDn0UoEzUTPIKxerAVsWF1Xp8
	RjYIS2zT7yGW9/3W/PRuYn96xJn4ToiP9p/rMwL7NYK+1KGa73hqZ3irCp77CrWy
	jPshB3Fdk2d0+kv6ephSuhQvjpJ5lxMYtWPFixX7Jkmndp4Dg=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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.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
MIME-Version:	1.0
Date:	Thu, 18 Sep 2014 08:35:13 +0200
From:	Markus Hoenicka <markus DOT hoenicka AT mhoenicka DOT de>
To:	Ken Brown <kbrown AT cornell DOT edu>
Cc:	cygwin <cygwin AT cygwin DOT com>, Eli Zaretskii <eliz AT gnu DOT org>
Subject:	Re: Strange gdb backtraces on 64-bit Cygwin
In-Reply-To:	<5419FB60.5090908@cornell.edu>
References:	<5419FB60 DOT 5090908 AT cornell DOT edu>
Message-ID:	<8e8c385f5fb29ba3d3853eeee61b34f6@mhoenicka.de>
X-Sender:	markus DOT hoenicka AT mhoenicka DOT de
User-Agent:	Roundcube Webmail
X-Df-Sender:	bWFya3VzLmhvZW5pY2thQG1ob2VuaWNrYS5kZQ==
X-IsSubscribed:	yes

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

- Raw text -