From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20039 invoked by alias); 27 Apr 2013 13:50:53 -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 20027 invoked by uid 89); 27 Apr 2013 13:50:53 -0000 X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-pd0-f174.google.com (HELO mail-pd0-f174.google.com) (209.85.192.174) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 27 Apr 2013 13:50:52 +0000 Received: by mail-pd0-f174.google.com with SMTP id y13so2512146pdi.5 for ; Sat, 27 Apr 2013 06:50:50 -0700 (PDT) X-Received: by 10.67.4.167 with SMTP id cf7mr35376384pad.62.1367070650776; Sat, 27 Apr 2013 06:50:50 -0700 (PDT) Received: from [192.168.1.128] ([115.193.12.195]) by mx.google.com with ESMTPSA id dr6sm17324081pac.11.2013.04.27.06.50.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Apr 2013 06:50:50 -0700 (PDT) Message-ID: <517BD8F6.8010806@gmail.com> Date: Mon, 29 Apr 2013 06:30:00 -0000 From: asmwarrior User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0a1 MIME-Version: 1.0 To: Eli Zaretskii CC: gdb-patches@sourceware.org Subject: Re: [RFA] Thread exit messages on MS-Windows References: <83obd1tyi7.fsf@gnu.org> <838v44tnf8.fsf@gnu.org> In-Reply-To: <838v44tnf8.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-04/txt/msg00846.txt.bz2 On 2013-4-27 15:58, Eli Zaretskii wrote: >> Date: Fri, 26 Apr 2013 12:46:56 +0300 >> From: Eli Zaretskii >> >> This is from the node "Threads" of the manual: >> >> `set print thread-events' >> `set print thread-events on' >> `set print thread-events off' >> The `set print thread-events' command allows you to enable or >> disable printing of messages when GDB notices that new threads have >> started or that threads have exited. By default, these messages >> will be printed if detection of these events is supported by the >> target. Note that these messages cannot be disabled on all >> targets. >> >> However, debugging MinGW programs on MS-Windows, I see only messages >> about new threads, like this: I'm not sure it is the correct behavior under Windows. When debugging a single thread app, I do receive one New Thread message (for the main thread of the inferior), but there is not corresponding exit thread message report for this main thread. For multiply thread apps, the first New Thread messages has no corresponding exit messages, but other threads have both new and their corresponding exit messages. Yuanhui Zhang BTW: Corresponding messages have the same thread ID like: [New Thread 2628.0xa4c] [Thread 2628.0xa4c exited with code 0]