Hi Mark,
Please try applying the patch from the 3.14.12 Known Problems page dated
2011-02-16 to your EPICS Base installation to see if it helps. This patch has
been reported to fix a couple of CA client issues at different sites now, and
if it helps you too I'll make it more prominent on that page.
http://www.aps.anl.gov/epics/base/R3-14/12-docs/KnownProblems.html
- Andrew
On Tuesday 08 March 2011 13:45:32 Vigder, Mark wrote:
> I'm running PyEpics 3.0.11, on Ubuntu 10.04.2, Epics 3-14-12, Python 2.6.5,
> linux-x86_64. A while ago (perhaps with earlier versions of something?)
> everything seemed to be working fine. I hadn't used it for a while, but now
> when I fire it up I end up with weird behaviour, e.g.:
>
> -I type: Motor('XXX:m1'). Returns error, saying 'XXX:m1' is not a motor.
>
> -I type: Motor('XXX:m1') a second time. This one works.
>
> -Sometime later, I'll get a 'Segmentation fault'.
>
> Anybody seen this kind of behaviour? Any ideas what's going on or where I
> should start looking for solutions?
>
> P.S., I just tried with Python3.1. Same thing.
>
> Thanks
> Mark
>
> Mark Vigder
> Canadian Neutron Beam Centre
--
An error is only a mistake if you don't learn from it.
When you learn something from it, it becomes a lesson.
- Replies:
- RE: PyEpics segmentation faults Vigder, Mark
- References:
- PyEpics segmentation faults Vigder, Mark
- Navigate by Date:
- Prev:
PyEpics segmentation faults Vigder, Mark
- Next:
RE: PyEpics segmentation faults Jeff Hill
- 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:
PyEpics segmentation faults Vigder, Mark
- Next:
RE: PyEpics segmentation faults Vigder, Mark
- 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
|