From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81887 invoked by alias); 21 Jun 2015 19:29:47 -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 81874 invoked by uid 89); 21 Jun 2015 19:29:46 -0000 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 Received: from limerock01.mail.cornell.edu (HELO limerock01.mail.cornell.edu) (128.84.13.241) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 21 Jun 2015 19:29:45 +0000 X-CornellRouted: This message has been Routed already. Received: from authusersmtp.mail.cornell.edu (granite3.serverfarm.cornell.edu [10.16.197.8]) by limerock01.mail.cornell.edu (8.14.4/8.14.4_cu) with ESMTP id t5LJThqD013661; Sun, 21 Jun 2015 15:29:43 -0400 Received: from [192.168.1.4] (cpe-67-249-176-138.twcny.res.rr.com [67.249.176.138]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id t5LJTf4L025749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 21 Jun 2015 15:29:42 -0400 Message-ID: <558710A4.5060309@cornell.edu> Date: Sun, 21 Jun 2015 19:29:00 -0000 From: Ken Brown 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@cygwin.com CC: Eli Zaretskii Subject: Re: gdb arbitrarily starting threads References: <20150620184715.GA17350@calimero.vinschen.de> <5585D052.2010009@cornell.edu> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-06/txt/msg00320.txt.bz2 On 6/20/2015 4:51 PM, William M. (Mike) Miller wrote: > On Sat, Jun 20, 2015 at 4:42 PM, Ken Brown 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