Zhong Ren wrote:
> Dear Noboru,
> Thank you. I must say the KEK CaPython314 is very easy to use.
> I am not surprised that your little test below won't crash,
> since it does not contain a wx.Timer. In order to repeat my
Each time I started the code, it crashes after some period but the
life-time varies time-to-time. Error message also changes.
I suspect interrupt caused by a timer breaks "Global-Interpreter-Lock"
mechanism, on which CA-Python interface relies on.
SWIG, a tool used in wxPython, supports threads and GIL but I'm not
quite sure if wxPython binary I got from the net uses this feature or
not. I want to check if this options affect the phenomena but it may
> crash, a wx.Timer must be constructed, it must be bound to a
> onTimer function, and it must be started. Using
> threading.Timer instead of wx.Timer will not cause the crash.
In my environment, threading.Timer also causes the crash. Whoom.
> I cannot tell who is guilty, wx.Timer or CaPython314. I also
> have the feeling that Python 2.5 may be the problem.
When I get the new result, I will report it on this mailing list.
tel;work:+81-29-864-1171, ext. 5309
- Re: wxPython timer and KEK CaPython314 cause core dump Zhong Ren
- Navigate by Date:
Re: [Fwd: EPICS Base @ HP-UX: Volunteers wanted] Billy Adams
Re: [Fwd: EPICS Base @ HP-UX: Volunteers wanted] Noboru Yamamoto
- Navigate by Thread:
Re: wxPython timer and KEK CaPython314 cause core dump Zhong Ren
next EPICS meeting at DESY in April 2007 Matthias Clausen