EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Call to assert failed - EPICS
From: "Hill, Jeff" <[email protected]>
To: Mark Rivers <[email protected]>, "'Pedro Mantovani Antunes'" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Tue, 28 Jun 2016 02:12:42 +0000

Hello Pedro,

 

Another possibility is data structure corruption originating from an unrelated thread. Is a newly developed device support in use for this particular motor?

 

Another possibility is an issue occurring due to the put-callback completing asynchronously in a different thread. The VxWorks “i” and “tt <task id>” commands can be run against the suspended thread to get a stack trace which might be helpful with understanding the issue. If this happens on Linux the gdb debugger can be used for the same purpose using gdb commands “info threads”, “thread nnn”, and “bt” for displaying a thread’s back trace. You will need to attach to the running process with “gdb <executable name> <process id>” command.

 

Jeff

 

From: Mark Rivers [mailto:[email protected]]
Sent: Monday, June 27, 2016 2:37 PM
To: 'Pedro Mantovani Antunes'; Hill, Jeff
Cc: [email protected]
Subject: RE: Call to assert failed - EPICS

 

Hi Pedro,

 

I see that you are using a version of EPICS base (3.14.10) that is almost 8 years old.  It is possible you are hitting a bug that has already been fixed.

 

Can you update to the current 3.14.12.5 version?

 

Are you using pyEpics?  If so, are you using the latest version of that?

 

Mark

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Pedro Mantovani Antunes
Sent: Monday, June 27, 2016 3:04 PM
To: [email protected]
Cc: [email protected]
Subject: Call to assert failed - EPICS

 

Mr. Hill,

 

I’m currently working at MRCAT (Section 10) at APS developing a program in python to set up the EPICS motors to the desired positions.

However, I’m getting an error when trying to move one specific motor (bl_angle). Below is the error message I’m getting:

 

A call to “assert (_pTargetMutex == & mutexToVerify)” failed in ../../../include/epicsGuards.h line 84.

EPICS Release EPICS R3.14.10 $R3-14-10$ $2008/10/27 19:39:04$.

Current time Mon Jun 27 2016 14:37:28.098931195.

Please E-mail this message to Jeff Hill [email protected] or to [email protected]

Calling epicsThreadSuspendSelf()

 

 

Also, this error only occurs with this specific motor, others are working fine.

Do you have any idea what this error message might be?

 

Thank you,

Pedro Mantovani Antunes


Replies:
RE: Call to assert failed - EPICS Pedro Mantovani Antunes
References:
Call to assert failed - EPICS Pedro Mantovani Antunes
RE: Call to assert failed - EPICS Mark Rivers

Navigate by Date:
Prev: RE: EPICS connect to siemens PLC317-2PN/DP: connetction problem XU Jie
Next: Compiling EPICS 3.14.12.5 with GCC 6 Luca Cavalli
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Call to assert failed - EPICS Mark Rivers
Next: RE: Call to assert failed - EPICS Pedro Mantovani Antunes
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Jul 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·