Dear All,
Thank you for the help.
Indeed the problem is related to a thread, as it only happens when I try to position the motor after the start of a new thread.
The team is now checking the possibility of updating epics.
However, I found a workaround by positioning the motor before the start of this thread. This causes the GUI to stutter while
It is moving, but it shouldn’t be a big problem.
Pedro Mantovani Antunes
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
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
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