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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-id:content-transfer-encoding
	:mime-version; q=dns; s=default; b=oA6QHTjGojXwVva6Kw/t48WVDNrtb
	VrndpZ4XxBJXz8fyWorCVQaNUnNt2m02WAUX1whX5TyseXQXeBHYcE6/c2EXLamW
	FktL24xIqGswR467q2hFSvfjjOSjqqcOXcLNwwlWeJtglpjwoZuv0xVckdd6FYHf
	AF1UTxmWS4/ItM=
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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-id:content-transfer-encoding
	:mime-version; s=default; bh=ATADDhjWLBu5aIm7r+B+jwlFGzY=; b=Jzu
	Hx6kp0uuGRTuuKrFqQh34HWfOJztOXVJ8E1zWbmvDSEIszzDu8Xo/6SVurCC2AOr
	T8T596wTzwDWIqobY1xXprAf1SvdMN1/ROpAfvF5y/aZ0hELd0/UjqVHkJ4zPywi
	ctAlvQkvMPgxBvLycEjQky91YRJai6u8kkpjAud4=
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-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=
X-HELO:	NAM05-DM3-obe.outbound.protection.outlook.com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cornell.edu; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GpahyITfgK+8E9VGsr0CxXvQuhd2lT/6Y2bDMxpwTjk=; b=Hj2CX3vXWwutnBI0FE73lOqtquedMlOlzwBFPw7f6wpntDNlGcEeigXeqpcV736DIxyyPuWYS20gFN3nA53ziSUWB4RxvtA9ZAXemJkcnqHDOkjCAij662zmVzgkD4QEoSPz3VCVBA8k+EOIjYCdsyYmeA3+Byf/jafikP5W0ZM=
From:	Ken Brown <kbrown AT cornell DOT edu>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Re: emacs-X11 freezes with mouse cut and paste
Date:	Thu, 4 Apr 2019 17:28:03 +0000
Message-ID:	<e8d10038-ef11-26e4-9d7a-cb0b8abcca30@cornell.edu>
References:	<fa6ec2233a744738b4efa74af9e9e68c AT vsrv060ex01 DOT ssd DOT fsi DOT com> <614fbba4-3425-4705-3342-99bbe8684ee0 AT cornell DOT edu> <94be9b602dbf4c02b6f7f796895b9475 AT vsrv060ex01 DOT ssd DOT fsi DOT com>
In-Reply-To:	<94be9b602dbf4c02b6f7f796895b9475@vsrv060ex01.ssd.fsi.com>
user-agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
authentication-results:	spf=none (sender IP is ) smtp.mailfrom=kbrown AT cornell DOT edu;
received-spf:	None (protection.outlook.com: cornell.edu does not designate permitted sender hosts)
x-ms-exchange-senderadcheck:	1
MIME-Version:	1.0
X-MS-Exchange-CrossTenant-mailboxtype:	HOSTED
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id x34HSHOq013410

On 4/4/2019 12:25 PM, Rockefeller, Harry wrote:
>> Alternatively, instead of running emacs under gdb, you could just run emacs as you normally do and then attach gdb when emacs freezes.  >("gdb -p <PID>")  At that point, a backtrace of all threads would be useful.

> It happened again.  Attached to PID as shown above.  (gdb) list gave same result as above.
> (gdb) bt
> #0  0x00000000773bafb1 in ntdll!DbgBreakPoint () from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
> #1  0x0000000077462e08 in ntdll!DbgUiRemoteBreakin () from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
> #2  0x00000000772659cd in KERNEL32!BaseThreadInitThunk () from /cygdrive/c/Windows/system32/kernel32.dll
> #3  0x000000007739a561 in ntdll!RtlUserThreadStart () from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
> #4  0x0000000000000000 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> 
> Does this tell me the problem is not Cygwin?  Perhaps BLODA or bad hardware, maybe bad mouse?

Not yet.  When you attach gdb to a process, it creates a new thread to be used 
by gdb.  What you're seeing above is the backtrace in that thread.  You need to 
switch to the main thread before you can get a useful backtrace:

(gdb) thread 1
(gdb) bt

Or you can just get a backtrace of all threads:

(gdb) thread apply all bt

The "info threads" command might clarify what's going on.

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

- Raw text -