This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Inadvertently run inferior threads
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb at sourceware dot org
- Date: Sat, 14 Mar 2015 19:01:23 +0200
- Subject: Re: Inadvertently run inferior threads
- Authentication-results: sourceware.org; auth=none
- References: <83h9tq3zu3 dot fsf at gnu dot org> <55043A63 dot 6020103 at redhat dot com> <8361a339xd dot fsf at gnu dot org> <5504555C dot 804 at redhat dot com> <83385736qt dot fsf at gnu dot org> <55045E87 dot 4040100 at redhat dot com> <83y4mz1rlr dot fsf at gnu dot org> <5504608C dot 6090004 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 14 Mar 2015 16:23:40 +0000
> From: Pedro Alves <palves@redhat.com>
> CC: gdb@sourceware.org
>
> >> It's the thread name, which defaults to the binary's file name name,
> >> which was "start-thread-infcall", but Linux trims it to 15 or so
> >> characters, IIRC. For this to work, you need to implement the
> >> target_thread_name hook. AFAICS, only linux-nat.c implements this.
> >
> > Well, Windows threads don't really have names, AFAIK.
>
> Last I looked, Visual Studio does support that. It's based on a
> funny hack:
>
> https://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx
That's only for viewing thread names in a debugger. Is that what
target_thread_name hook does?