From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27562 invoked by alias); 20 Jun 2015 20:42:48 -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 27552 invoked by uid 89); 20 Jun 2015 20:42:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: limerock04.mail.cornell.edu Received: from limerock04.mail.cornell.edu (HELO limerock04.mail.cornell.edu) (128.84.13.244) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 20 Jun 2015 20:42:46 +0000 X-CornellRouted: This message has been Routed already. Received: from authusersmtp.mail.cornell.edu (granite3.serverfarm.cornell.edu [10.16.197.8]) by limerock04.mail.cornell.edu (8.14.4/8.14.4_cu) with ESMTP id t5KKgia1003252 for ; Sat, 20 Jun 2015 16:42:44 -0400 Received: from [192.168.1.3] (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 t5KKghvm009853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sat, 20 Jun 2015 16:42:43 -0400 Message-ID: <5585D052.2010009@cornell.edu> Date: Sat, 20 Jun 2015 20:42: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 Subject: Re: gdb arbitrarily starting threads References: <20150620184715.GA17350@calimero.vinschen.de> 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/msg00312.txt.bz2 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. I'm not seeing this on my system (Windows 7, both 32-bit and 64-bit Cygwin). I debugged the emacs source, set a breakpoint, and stepped through the program when the breakpoint was hit. Could this be caused by BLODA interference (https://cygwin.com/faq/faq.html#faq.using.bloda)? 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