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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | PyEpics segmentation faults |
From: | "Vigder, Mark" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Tue, 8 Mar 2011 14:45:32 -0500 |
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
|