From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11806 invoked by alias); 11 Jun 2013 17:05:34 -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 11794 invoked by uid 89); 11 Jun 2013 17:05:33 -0000 X-Spam-SWARE-Status: No, score=-4.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,SPF_SOFTFAIL autolearn=no version=3.3.1 Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 11 Jun 2013 17:05:32 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MO800C00NE9NV00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Tue, 11 Jun 2013 20:05:24 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MO800CQINH0AM80@a-mtaout20.012.net.il>; Tue, 11 Jun 2013 20:05:24 +0300 (IDT) Date: Tue, 11 Jun 2013 17:40:00 -0000 From: Eli Zaretskii Subject: Re: [commit/windows] Add thread ID in SuspendThread error warning message. In-reply-to: <20130611162738.GN3969@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ppvslgrq.fsf@gnu.org> References: <1370946106-7883-1-git-send-email-brobecker@adacore.com> <8338somyrk.fsf@gnu.org> <20130611162738.GN3969@adacore.com> X-SW-Source: 2013-06/txt/msg00261.txt.bz2 > Date: Tue, 11 Jun 2013 18:27:38 +0200 > From: Joel Brobecker > Cc: gdb-patches@sourceware.org > > > 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. Sadly, no. I tried to reproduce it, but it never happens when I want it to, and I couldn't until now figure out what are the conditions for that to happen. I actually thought it was a bug in the program I was debugging (Emacs), which made this warning even more important. > > 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 will try to find time.