Hi Christian,
The failure indicates to me a problem in your code, because it should not happen. The failure is happening in pasynManager->lockPort(). Is your code calling that function explicitly?
Is the failure reproducible?
Is this on Linux? If so, you can generate a core file and run gdb on it to get a traceback.
Mark
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Christian Pulvermacher
Sent: Sunday, November 13, 2016 11:35 PM
To: tech-talk
Subject: mutex lock assertion failure
Hello,
I encountered the following assertion failure in one of our IOCs. Is this EPICS-internal, or something that can originate from our own code?
> A call to 'assert(status == epicsMutexLockOK)'
> by thread 'jtag:dhh.hll0' failed in ../../asyn/asynDriver/asynManager.c line 1694.
> EPICS Release EPICS R3.14.12.5-belle2 $Date: Tue 2015-03-24 09:57:35 -0500$.
> Local time is 2016-11-09 10:44:18.525347533 JST
> Please E-mail this message to the author or to [email protected]
Kind regards,
Christian
- Replies:
- RE: mutex lock assertion failure Christian Pulvermacher
- References:
- mutex lock assertion failure Christian Pulvermacher
- Navigate by Date:
- Prev:
RE: FLOOR function in EPICS CALC error rory.clarke
- Next:
Re: OS X edm/medm openmotif woes J. Lewis Muir
- 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
- Navigate by Thread:
- Prev:
mutex lock assertion failure Christian Pulvermacher
- Next:
RE: mutex lock assertion failure Christian Pulvermacher
- 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
|