This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Thread exit messages on MS-Windows
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 29 Apr 2013 18:30:39 +0300
- Subject: Re: [RFA] Thread exit messages on MS-Windows
- References: <83obd1tyi7 dot fsf at gnu dot org> <838v44tnf8 dot fsf at gnu dot org> <87li817699 dot fsf at fleche dot redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 29 Apr 2013 08:37:06 -0600
>
> >>>>> "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.
If we decide to do this in delete_thread, then we will have to remove
the announcements in several target-specific files which do that, like
linux-nat.c. Is that OK?