From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 45995 invoked by alias); 22 Jun 2015 00:28:53 -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 45987 invoked by uid 89); 22 Jun 2015 00:28:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yh0-f44.google.com Received: from mail-yh0-f44.google.com (HELO mail-yh0-f44.google.com) (209.85.213.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 22 Jun 2015 00:28:51 +0000 Received: by yhan67 with SMTP id n67so96614093yha.3 for ; Sun, 21 Jun 2015 17:28:49 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.13.217.147 with SMTP id b141mr13656595ywe.22.1434932929096; Sun, 21 Jun 2015 17:28:49 -0700 (PDT) Received: by 10.13.195.4 with HTTP; Sun, 21 Jun 2015 17:28:49 -0700 (PDT) In-Reply-To: <558710A4.5060309@cornell.edu> References: <20150620184715.GA17350@calimero.vinschen.de> <5585D052.2010009@cornell.edu> <558710A4.5060309@cornell.edu> Date: Mon, 22 Jun 2015 00:28:00 -0000 Message-ID: Subject: Re: gdb arbitrarily starting threads From: "William M. (Mike) Miller" To: cygwin@cygwin.com Cc: Eli Zaretskii Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-06/txt/msg00321.txt.bz2 On Sun, Jun 21, 2015 at 3:29 PM, Ken Brown wrote: > 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. Thanks to Eli for the work on tracking this down! It certainly is annoying, so I'll definitely keep my eye out for a 7.10 announcement. Thanks for the info. -- 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