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:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=Fu 40egPKamrBIrZ5LQxW/BywSJHHUyA3HfYqq20qb3J03cuWHpidLX2rnPffgZFQ67 fdlTTgiU6mhhBMOIOmik6QXKOZBdqOUuy9xmc0XB+w/GlLvA4Oe56WWW6uvnVTF4 MVQMEbuzOhDb7f4dhmTjqSbGxt3CSI2tnVBV6owzM= 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:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=Z+IPi3AM F0c34sqJF2+ZEG7EuO0=; b=URgAt07+G/9LsbtZNLpfgwxyA1mgnEDTUPHjVqIu nqZf+Jw3Ny8S5I+nDe34fiHipviaZ9MpuhQTJmbkOMZbNxaPdHsHd1ECLW1IxxXT 1FBouBcxcf1DE1IoqBpAgczqIF3noLcvnpYx6qt7cHUD5HTw6/rMwojxEmnu5oiA vbA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=0.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yk0-f182.google.com MIME-Version: 1.0 X-Received: by 10.13.255.132 with SMTP id p126mr2014527ywf.157.1434833494030; Sat, 20 Jun 2015 13:51:34 -0700 (PDT) In-Reply-To: <5585D052.2010009@cornell.edu> References: <20150620184715 DOT GA17350 AT calimero DOT vinschen DOT de> <5585D052 DOT 2010009 AT cornell DOT edu> Date: Sat, 20 Jun 2015 16:51:33 -0400 Message-ID: Subject: Re: gdb arbitrarily starting threads From: "William M. (Mike) Miller" To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes 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. > > > I'm not seeing this on my system (Windows 7, both 32-bit and 64-bit Cygwin). I'm running 8.1, so that could well be the difference there. > 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)? I certainly won't say that it's impossible, but I think it's unlikely. The symptoms mentioned there don't seem related. Also, the only one of those programs I'm using is Windows Defender, and I've been using it for over two years, but this problem only started within the last few months. (Of course, I suppose it's possible that something in Cygwin/gdb/gcc changed to make it more sensitive, or an update to Windows Defender made it more intrusive...) Failing a way to keep gdb from doing this, is there a way in gdb to stop a thread that's in "(running)" state? (Even though it's sitting at a breakpoint.) -- William M. (Mike) Miller | Edison Design Group william DOT m DOT miller AT gmail DOT com -- 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