Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Thread exit messages on MS-Windows
Date: Mon, 29 Apr 2013 19:26:00 -0000	[thread overview]
Message-ID: <87li817699.fsf@fleche.redhat.com> (raw)
In-Reply-To: <838v44tnf8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Apr	2013 10:58:35 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

>> In thread.c, I see that add_thread_with_info will announce new threads
>> if print_thread_events is non-zero, but I see no similar announcement
>> in delete_thread or its subroutines.  Is this supposed to be handled
>> by target-specific back ends?  I see something like that in, e.g.,
>> linux-nat.c and in inf-ttrace.c, but I'm unsure whether that is a
>> conclusive evidence.
>> 
>> If indeed thread deletion should be announced by the target, why this
>> asymmetry with thread creation?

Eli> No one replied, so I'm now converting this into an RFA.  The patch
Eli> below causes GDB on Windows to display thread exit messages like this:

I didn't answer, but I also wonder why it is not done by delete_thread.

Tom


  parent reply	other threads:[~2013-04-29 14:37 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
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 [this message]
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=87li817699.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --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