[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [cdt-dev] OT: Setting thread names (was: Displaying thread namesin debug view)
|
Johan,
we are doing this with eCos (http://ecos.sourceware.org/) whose cyg_thread_create() method accepts a thread name. As far as I know naming threads is supported by the POSIX API, but many embedded OSes do support it.
Greets
Norbert
-----Ursprüngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Johan Walles
Gesendet: Montag, 8. August 2005 11:03
An: CDT General developers list.
Betreff: Re: [cdt-dev] OT: Setting thread names (was: Displaying thread namesin debug view)
Do you know if pthreads supports setting thread names? If so, how do I
set the name of a thread?
Regards //Johan
Ploett Norbert wrote:
> Hello folks,
>
> a colleague of mine was wondering why the debug view does not display
> thread names when the gdb debugger does return them when queried with
> "info threads":
>
> ===================
> [1.123.068.100.723] 16 info threads
> [1.123.068.100.723] (gdb)
> [1.123.068.100.723] ~"info threads\n"
> [1.123.068.100.793] ~" 5 Thread 8 ( Name: TIMERThread, State: sleeping,
> Priority: 14 ) "
> [1.123.068.100.843] ~" 4 Thread 3 ( Name: Network support, State:
> sleeping, Priority: 7 ) "
> [1.123.068.100.893] ~" 3 Thread 2 ( Name: Network alarm support, State:
> sleeping, Priority: 6 ) "
> [1.123.068.100.953] ~" 2 Thread 1 ( Name: Idle Thread, State: ready,
> Priority:31 ) "
> [1.123.068.100.993] ~"* 1 Thread 9 ( Name: pthread.00000800, State:
> running, Priority: 15 ) "
> ===================
>
> I looked into it and found the follwing:
>
> - org.eclipse.cdt.debug.mi.core.output.CLIInfoThreadsInfo analyzes the
> gdb output.
> - CLIInfoThreadsInfo.getThreadNames() currently simply returns null.
> - CLIInfoThreadsInfo.parseThreadInfo(String, List) currently only parses
> for the thread number.
> - It is easy to augment parseThreadInfo(String, List) so that it
> retrieves the thread name along with the number and then properly
> implement getThreadNames(). This is sufficient for getting the thread
> names displayed in the debug view.
>
> Now we would find it a very handy feature to have the thread names and
> would do the implementation and supply the patches and all this. My
> question to the community are:
>
> - Would this solution be accepted? Did I overlook anything?
> - Can I proceed to create a bugzilla entry?
> - Who will evaluate the patches?
> - For which version of CDT will it be available?
>
> Thanks for answers,
>
>
> Norbert Ploett
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
