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  <20112012  2013  2014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: RE: PyEpics segmentation faults
From: "Vigder, Mark" <Mark.Vigder@nrc-cnrc.gc.ca>
To: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Tue, 8 Mar 2011 17:40:46 -0500
Andrew/Jeff

Thanks for the patch suggestions. Turns out the problem was PyEpics 3.0.11 on 64 bit systems. Matt had already fixed it with the latest version that was in the repository.

I certainly appreciate the help.

Mark

________________________________________
From: Andrew Johnson [anj@aps.anl.gov]
Sent: March 8, 2011 3:16 PM
To: tech-talk@aps.anl.gov; Vigder, Mark
Subject: Re: PyEpics segmentation faults

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 Matt Newville
References:
PyEpics segmentation faults Vigder, Mark
Re: PyEpics segmentation faults Andrew Johnson

Navigate by Date:
Prev: EDM X/Y Eric Norum
Next: Asyn/Modbus Delay Robert Emery
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: PyEpics segmentation faults Andrew Johnson
Next: Re: PyEpics segmentation faults Matt Newville
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·