Subject: |
Re: [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 |
From: |
mdavidsaver via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Mon, 06 May 2019 22:39:55 -0000 |
I think that either the "caClientCallbackThreadId = 0;" needs to be restored, or cacExitHandler() completely removed.
Also, the epicsAtExit() callback ordering in pyDevSup has separately been addressed.
https://github.com/mdavidsaver/pyDevSup/pull/20
--
https://code.launchpad.net/~info-martin-konrad/epics-base/+git/epics-base/+merge/366996
Your team EPICS Core Developers is subscribed to branch epics-base:3.15.
- References:
- [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 Martin Konrad via Core-talk
- Navigate by Date:
- Prev:
Re: [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 Martin Konrad via Core-talk
- Next:
Re: [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 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:
Re: [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 Martin Konrad via Core-talk
- Next:
Re: [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 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
|