Le mercredi 28 mars 2018 à 16:16 +0200, Philippe Gerum a écrit :
>
> cobalt_thread_pid(pthread_t) from the internal support library would
> do
> the job. A successful call would denote a cobalt thread, -ESRCH would
> denote a regular (or invalid) pthread.
Seems to work perfectly, thanks.
On 03/28/2018 04:00 PM, Julien Blanc wrote:
> We're using a mix of regular NPTL posix threads and RT cobalt threads
> in our application, using XDDP communication between them.
>
> In a few places, we need to identify the calling context, ie, whether
> we're being called from a cobalt RT thread
We're using a mix of regular NPTL posix threads and RT cobalt threads
in our application, using XDDP communication between them.
In a few places, we need to identify the calling context, ie, whether
we're being called from a cobalt RT thread or from a regular NPTL
thread, and act accordingly.
My
