From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 39649 invoked by alias); 20 Jun 2015 20:51:38 -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 39641 invoked by uid 89); 20 Jun 2015 20:51:37 -0000 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 Received: from mail-yk0-f182.google.com (HELO mail-yk0-f182.google.com) (209.85.160.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Sat, 20 Jun 2015 20:51:36 +0000 Received: by ykdt186 with SMTP id t186so5395127ykd.0 for ; Sat, 20 Jun 2015 13:51:34 -0700 (PDT) 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) Received: by 10.13.195.4 with HTTP; Sat, 20 Jun 2015 13:51:33 -0700 (PDT) In-Reply-To: <5585D052.2010009@cornell.edu> References: <20150620184715.GA17350@calimero.vinschen.de> <5585D052.2010009@cornell.edu> Date: Sat, 20 Jun 2015 20:51:00 -0000 Message-ID: Subject: Re: gdb arbitrarily starting threads From: "William M. (Mike) Miller" To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-06/txt/msg00313.txt.bz2 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.m.miller@gmail.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