Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Thread exit messages on MS-Windows
Date: Mon, 29 Apr 2013 06:30:00 -0000	[thread overview]
Message-ID: <83wqrormpc.fsf@gnu.org> (raw)
In-Reply-To: <517BD8F6.8010806@gmail.com>

> 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]


  reply	other threads:[~2013-04-27 15:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83obd1tyi7.fsf@gnu.org>
2013-04-28 16:24 ` Eli Zaretskii
2013-04-29  4:32   ` Eli Zaretskii
2013-04-29  8:21     ` Corinna Vinschen
2013-04-29  8:38       ` Eli Zaretskii
2013-04-29  5:09   ` asmwarrior
2013-04-29  6:30     ` Eli Zaretskii
2013-04-29  6:30   ` asmwarrior
2013-04-29  6:30     ` Eli Zaretskii [this message]
2013-04-29 17:31   ` Joel Brobecker
2013-04-29 20:27     ` Eli Zaretskii
2013-04-30 11:51       ` Joel Brobecker
2013-04-29 19:26   ` Tom Tromey
2013-04-30  0:58     ` Eli Zaretskii
2013-04-30 11:38       ` Joel Brobecker
     [not found]         ` <83obcwoubz.fsf@gnu.org>
2013-05-01  5:14           ` Joel Brobecker
2013-05-04 13:40             ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wqrormpc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=asmwarrior@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox