From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-100921-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 13233 invoked by alias); 27 Apr 2013 15:57:21 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 13224 invoked by uid 89); 27 Apr 2013 15:57:21 -0000
X-Spam-SWARE-Status: No, score=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL,TW_SM 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; Sat, 27 Apr 2013 15:57:19 +0000
Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MLX00J00886G500@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Sat, 27 Apr 2013 18:57:16 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MLX00I8Y8BGXHC0@a-mtaout20.012.net.il>; Sat, 27 Apr 2013 18:57:16 +0300 (IDT)
Date: Mon, 29 Apr 2013 06:30:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] Thread exit messages on MS-Windows
In-reply-to: <517BD8F6.8010806@gmail.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83wqrormpc.fsf@gnu.org>
References: <83obd1tyi7.fsf@gnu.org> <838v44tnf8.fsf@gnu.org> <517BD8F6.8010806@gmail.com>
X-SW-Source: 2013-04/txt/msg00847.txt.bz2

> Date: Sat, 27 Apr 2013 21:56:06 +0800
> From: asmwarrior <asmwarrior@gmail.com>
> CC: gdb-patches@sourceware.org
> 
> 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.

This is on purpose: I think announcing the death of the main thread is
redundant, because it is always followed by this:

  [Inferior 1 (process 4216) exited normally]