Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0

[Andrew Johnson via Core-talk <core-talk@aps.anl.gov>]

The VxWorks implementation of osdThread is pretty thin — our thread ID is the OS's task ID, and in various places the code assumes the system is UP, so no memory barriers are required. I don't understand where else you could see races or user-after-frees that don't also exist in the native taskWait() API. Wind River implements taskWait() by adding the calling task to a wait queue that lives in the TCB of the task being waited for. The queue gets flushed (by a different task) to wake up all waiters when the task is deleted.

Now I agree that the current code is too simple since it doesn't check the status returned by taskWait() or look at errno, which obviously needs to be done and the subsequent behavior made to match the other implementations. I skipped doing that to have the discussion about returning an error status.

-- 
https://code.launchpad.net/~epics-core/epics-base/+git/Com/+merge/361379
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.