Subject: |
Re: [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 |
From: |
Martin Konrad via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Mon, 06 May 2019 17:55:37 -0000 |
Oops, of course you're right. I guess taking out the epicsThreadPrivateDelete() call is not really an option either because then the object is leaked...
I guess the right approach would be to use a shared pointer to get it cleaned up when it's not used anymore. But that would obviously break the interface (not sure if we can avoid this here, though). Any thoughts?
--
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 mdavidsaver via Core-talk
- Next:
Build failed in Jenkins: epics-base-3.15-sol #187 APS Jenkins 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 mdavidsaver 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 mdavidsaver 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
|