| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy |
| From: | Jameson Graef Rollins <[email protected]> |
| To: | "Wang Xiaoqiang \(PSI\)" <[email protected]>, Michael Davidsaver <[email protected]> |
| Cc: | Epics <[email protected]> |
| Date: | Fri, 15 May 2015 12:27:19 -0700 |
On Fri, May 15 2015, "Wang Xiaoqiang (PSI)" <[email protected]> wrote: > Thanks for the hints. In pcaspy library, the PV instances are created on startup and live until application quits. > The casPV::destroy method is not implemented. > https://github.com/paulscherrerinstitute/pcaspy/blob/master/pcaspy/pv.cpp#L112 How is the garbage collection handled? Since the problem does seem to occur when subscriptions are disconnected, presumably something is destroyed at that point. > But it does implement casPV::createChannel for access security group. > Will that cause this double free problem? FWIW we're not using any access control in our application. jamie.
Attachment:
signature.asc
Description: PGP signature