Subject: |
Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 |
From: |
mdavidsaver via Core-talk <[email protected]> |
To: |
mdavidsaver <[email protected]> |
Date: |
Wed, 19 Jun 2019 17:16:26 -0000 |
> This almost seems too simple...
Unfortunately, yes. I think this is open to races involving re-use of thread IDs (and maybe use after free?). This potential is why the RTEMS version uses a barrier to prevent the thread from actually returning until it is joined (the rtems_id stays valid). Alternately, as with WIN32, allocated a separate epicsThreadId, with a ref. counter, that can outlive the OS task.
--
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.
- Navigate by Date:
- Prev:
Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk
- Next:
Re: IOC Threads blocking all signals Ralph Lange via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
2025
- Navigate by Thread:
- Prev:
Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk
- Next:
Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
2025
|