Yes, it needs more work.
Mircea Gherzan has created Bugzilla to rework pthread_setname_np() usage:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=568541
Regards,
Eugene
From: tcf-dev-bounces@xxxxxxxxxxx <tcf-dev-bounces@xxxxxxxxxxx>
On Behalf Of Joel Sherrill
Sent: Thursday, November 5, 2020 12:25 PM
To: TCF Development <tcf-dev@xxxxxxxxxxx>
Subject: [tcf-dev] Setting Thread Name
CAUTION: This message has originated from an External Source. Please use proper judgment and caution
when opening attachments, clicking links, or responding to this email.
Hi
For RTEMS, I am starting the tcf agent main called from a wrapper thread method that passes in the arguments. This lets me control the priority and stack size of the agent thread. When using the thread introspection commands available in
the RTEMS shell, I noticed that
+ main.c creates a thread signal_handler_thread() which has no name because it doesn't call pthread_setname_np().
+ pthread_setname_np() must be universally available or someone else would have mentioned that this is a common non-portable (e.g. _np) POSIX extension. Should the use of this method be conditionalized? RTEMS has this method too so it isn't
a porting issue for me. It is just a matter of sticking to portable methods.
--joel