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:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=m9mj2M52nAc+tJZI
	elgmfMsyz/cYK4rvh7xVe0GwXrKqD0heOvRMRZ1HIlzXH/OxXEN5aNTUnPYbpMjC
	ldUgU9suXaghc50tU68m6fKswDHxa7tzXM5ZQ8PXfm8b7YQfrA58QeNJgn8j7Vcj
	Ect0rnEhhJr6kE2QEEVUDU59m4Y=
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:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=L3rZ0pBNPks3d9vv5SJsHm
	EtuIY=; b=JhiLlVUqbLTTOZHM7aeU4az9mYSCSR7jZPpCyIh5OmZ97NQtm1wjzg
	jHWJ9fot3aq6w4sACo/5kvdCr/XGDpmThhz4hMSL9xX0+lHPNvCv3QLb8CRzl2M1
	Xm5lgsCJDya039wm7VzIzwWY5rozIdQi2qyD9pnnYiB+w02sjN6kc=
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=-2.5 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: <558710A4.5060309@cornell.edu>
Date: Sun, 21 Jun 2015 15:29:40 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: gdb arbitrarily starting threads
References: <CAH5rLZVsTzSVTRzG_Aucw=_i-o5M-G0_ddPu0gPaqQM-Nn3iJg AT mail DOT gmail DOT com>	<20150620184715 DOT GA17350 AT calimero DOT vinschen DOT de>	<CAH5rLZXbYNUwB_f2Vigev--NsmB3FrdhWre1uYxAr0ckN8NvmQ AT mail DOT gmail DOT com>	<5585D052 DOT 2010009 AT cornell DOT edu> <CAH5rLZU6mbwex-EM81N0TFpauoZ23ZJsAU0D6M1H3APzZmdO9w AT mail DOT gmail DOT com>
In-Reply-To: <CAH5rLZU6mbwex-EM81N0TFpauoZ23ZJsAU0D6M1H3APzZmdO9w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 6/20/2015 4:51 PM, William M. (Mike) Miller wrote:
> On Sat, Jun 20, 2015 at 4:42 PM, Ken Brown <kbrown AT cornell DOT edu> wrote:
>> On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote:
>>>
>>> Thanks for the reply.  My concern, however, isn't that new threads are
>>> being created; it's that when gdb does this, it sets the state of all
>>> threads, including my main thread, to "(running)" so that I can't
>>> single-step through my program any more.  If I try to say "next", I
>>> get the error:
>>>
>>>       Cannot execute this command while the selected thread is running.
>>>
>>> But I did nothing overt to start my thread.
>>>
>>> It never used to do this, but it happens regularly now.

Eli Zaretskii has asked me to pass on the following information:

On 6/21/2015 2:43 PM, Eli Zaretskii wrote:
 > Please point the people discussing this on the Cygwin list to these 2
 > threads on GDB mailing lists:
 >
 >    https://sourceware.org/ml/gdb/2015-03/msg00024.html
 >    https://sourceware.org/ml/gdb/2015-06/msg00005.html
 >    https://sourceware.org/ml/gdb-patches/2015-06/msg00215.html
 >
 > Bottom line: (1) it happens on Windows 7, not just on 8.1; (2) it
 > happens in the MinGW build of GDB, and so is not specific to threads
 > started by Cygwin for its own purposes; (3) it will most probably be
 > solved soon, since it is currently blocking the release of the
 > upcoming GDB 7.10.

Please keep Eli in the CC on any replies since he is not subscribed to the 
Cygwin list.

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