From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1307 invoked by alias); 11 Jun 2013 16:27:43 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 1244 invoked by uid 89); 11 Jun 2013 16:27:42 -0000 X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO autolearn=ham version=3.3.1 Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 11 Jun 2013 16:27:41 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E14F52EE1A; Tue, 11 Jun 2013 12:27:39 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3df8PmVYGV4d; Tue, 11 Jun 2013 12:27:39 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id AFCF22EBA7; Tue, 11 Jun 2013 12:27:39 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 59103C2B35; Tue, 11 Jun 2013 20:27:38 +0400 (RET) Date: Tue, 11 Jun 2013 16:38:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [commit/windows] Add thread ID in SuspendThread error warning message. Message-ID: <20130611162738.GN3969@adacore.com> References: <1370946106-7883-1-git-send-email-brobecker@adacore.com> <8338somyrk.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8338somyrk.fsf@gnu.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-06/txt/msg00258.txt.bz2 > Thanks, I see these on Windows 7 (but not on XP) as well, and wonder > what they mean and what causes them. If you have a reproducer, it would be helpful to me. I wasn't able to reproduce locally, and this trace would have helped, but the person experiencing the problems no longer has the time to re-do all the experiments for the time beeing. So the pressure is less, but I am definitely curious to know what's causing this. > Btw, wouldn't it be better to show the process ID as well, as in > 0x1234.0x720, for consistency with how we show threads in other > contexts, like "New thread" etc? Might be a good idea indeed. Would you like to send a patch? I've switched context to something that's going to take me a day or two, so I'd rather not worry about that for now. If not, I'll keep that in my TODO, and send a patch maybe next week. -- Joel