** Changed in: epics-base/3.16
Status: Fix Committed => Fix Released
** Changed in: epics-base/3.15
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1730982
Title:
Race in db_close_events()
Status in EPICS Base:
Fix Released
Status in EPICS Base 3.14 series:
Won't Fix
Status in EPICS Base 3.15 series:
Fix Released
Status in EPICS Base 3.16 series:
Fix Released
Status in EPICS Base 7.0 series:
Fix Released
Bug description:
valgrind reports a data race in db_close_events(). This is the
pattern of:
> epicsEventMustWait(...)
> epicsEventDestroy(...)
Where the working calling 'epicsEventSignal(...)' may not have
returned before the event is destroy'd.
I introduced this race in d2b0e920012d4c9bc0eaecc0e092cedd776db578
prior to 3.15.0.1 to fix a similar race (the worker was calling
epicsEventDestroy() ).
We need a safe pattern for joining worker threads (cf. lp:1699229).
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1730982/+subscriptions
- Navigate by Date:
- Prev:
[Bug 1699229] Re: Joinable threads Andrew Johnson via Core-talk
- Next:
[Bug 1842086] Re: TestHarness should be TESTPROD instead of PROD 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
- Navigate by Thread:
- Prev:
[Bug 1699229] Re: Joinable threads Andrew Johnson via Core-talk
- Next:
Build failed: EPICS Base base-R7.0.3.1-478 AppVeyor 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
|