| 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: Strange error in EPICS client program |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Jörn Dreyer <j.dreyer at hzdr.de> |
| Cc: | tech-talk at aps.anl.gov |
| Date: | Fri, 22 Sep 2023 08:41:02 -0700 |
On 9/22/23 01:19, Jörn Dreyer via Tech-talk wrote:
Hello, I recently run into a problem with a client code that throws strange errors at me during runtime:CA client library tcp recieve thread terminating due to C++ exception"epicsMutex::invalidMutex()"
"invalidMutex" indicates a coding error. (NULL dereference, memory corruption, use-after-free, ...) Hopefully you can reproduce this error quickly, I would suggest running in GDB and setting a breakpoint on the exception class ctor 'epicsMutex::invalidMutex::invalidMutex()'. Then look for signs of corruption.
epicsMutex pthread_mutex_lock failed: error epicsMutexOSDLock epicsThread: Unexpected C++ exception "epicsMutex::invalidMutex()" with type"N10epicsMutex12invalidMutexE" in thread "CAC-TCP-send" at XXXterminate called after throwing an instance of 'epicsMutex::invalidMutex()' what(): epicsMutex::invalidMutex()After that my program crashes. Can anybody shed some light on that. It was running all good until two days ago when this error started to pop up when a connection to a PV is made. Regards, Jörn Dreyer